|Re: [eclipse.org-architecture-council] The Art of Project Release Naming|
Esteemed members of the Eclipse AC,How do you handle naming within your projects? There was some discussion that sparked my interested on the ECF mailing list recently...In essence, it boiled around versioning things properly and from that... what to call your project when referring to a release.I have noticed in Galileo, projects like CDT seems to just increment a version each release. I don't know if the CDT team is doing this as a marketing thing only or actually revving bundle versions when they shouldn't be. I find it software engineering has unfortunately taught us to treat versions as a marketing number :(In the end, the issue I want to bring up is if the AC thinks recommending a project release naming scheme is important?Should we be consistent across projects and maybe recommend that projects name things to align with the train?CDT Galileo vs. CDT 6.0?ECF Helios vs. ECF 4.0?Thoughts?Cheers,
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
eclipse.org-architecture-council mailing list
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
Back to the top