|RE: [cross-project-issues-dev] Best practices on versioning|
To take some heat off EMF J, we do the same in the CDT. What is best practices for some is not as good for others. The CDT does not have a release engineering team. In fact, I am the CDT release engineer. Since I have many hats, I do not have much time to spend on writing build scripts and am reluctant to change them. So for us, not using the releng tools and simply tagging and building all the plugins every build was easy to do, it works, and I don’t have the time right now to change them. This is also why I am against the pack200 thing BTW.
Now as the next simultaneous release rolls around again next year, I think this is one area where we could really reduce duplication in the projects and streamline things. I would like to propose that we have one release engineering team, with maybe participants from various projects, working on one single set of build scripts and a single simultaneous build. This would solve a lot of problems, including the lag we have between Platform build and Callisto release, and it would make it easier for us to line up with “best practices”. On the negative side, there is much more chance for these builds to be busted as API changes occur in the lower bits, but then I think that would also force the lower bit teams and the upper bit teams to communicate more.
Any, just a thought and sorry for not following “best practices”.
Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, Tools PMC member
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Back to the top