Open mmarquar opened 5 years ago
Hi @mmarquar, welcome to the epicsdeb project! I'm glad to hear that you are considering to contribute - we can always use some helping hands :-) You can contribute by submitting issue tickets, creating pull requests or by testing new releases.
Unfortunately @mdavidsaver and I will not be able to attend the EPICS meeting in person. I'm not sure about @aderbenev. At FRIB I'm currently working on getting 3.15.6 packaged and deployed. At the same time I'm trying to resolve issues on Debian stretch. Once that's done (maybe by the end of the year) we are planning to start working on packaging EPICS 7. We are intending to skip 3.16 and want to move directly to 7. Base 3.16 and 7 are pretty similar when it comes to the EPICS 3 part and adding the EPICS 4 part doesn't hurt ;-)
When it comes to packaging 3.16 or 7, I would recommend to start with my 3.15.6 branch.
+1 for skipping 3.16 3.16.1 has a few really nasty bugs that are fixed in 7.0. The immanent 3.16.2 release will be the last one in the 3.16 series, which will be dropped.
Try checking out the 7.0 branch without submodules - surprise: it will work, and build exactly the V3 scope.
I concur on all above - with our legacy-ish-ness in places, there would be no real demand to upgrade to and test the 3.16. Plus, we already have EPICS 7 and modules binary bundles (not from Debian packaging) used for AreaDetector IOCs. I won't be attending the meeting alas, but Kunal is coming - he's not involved in packaging much, but can bring your insights to us at NSLS-II.
We (CSIRO ASKAP) are just about to move to 3.16.1 as preparation for 7. Currently, we just create debian binary packages from our build system (3.14.x and 3.16.1)which are not supposed to comply to policies and are single platform. We have been looking at this project and like to move and possibly contribute to this. Is anyone coming to the collab meeting in Melbourne next month? We could discuss this furher then.