v5 Tracking Issue

[tomeichlersmith]

I just want to formally list which issues will be resolved for the next major release. I think changing the underlying OS and ROOT versions then motivate a new major version.

[tomeichlersmith]

@bloodyyugo @tvami @EBerzin y'all are the folks I know who have worked with ldmx-sw/Tracking and acts. I am interested in including acts in the development image since ldmx-sw developers aren't editing it themselves and it takes a long time to build. The natural downside of this is then the acts version is more strictly frozen being tied with the image version rather than the submodule reference in ldmx-sw. How comfortable are you guys with freezing the acts version? v36 is not the latest anymore, but do you see us needing/wanting to upgrade on a faster time scale than image releases? We'd also need to be able to support multiple acts versions if we wanted to upgrade within the image so that we don't necessarily require developers to upgrade their image which might be too much of a headache as well.

[tvami]

I agree that putting ACTS to the dev image is going to be very helpful, v36 seems stable enough, and if we update, it can go together with an image update too

[bloodyyugo]

I think this is fine. We are not planning on keeping up with ACTs release-for-release and things seem to be working as of now. We will probably upgrade again later this year as it looks (just looking through their github) like there are some minor fixes/improvements that be applicable to us. But, we change just update the image as Tamas said.