Le 14/08/2017 à 22:36, Jesse McConnell a écrit : > Something we have learned with Jetty and our adoption of osgi versioning is > that most anything beyond normal versioning really confuses people. We > have had an embarrassing amount of people think a M# release (supposedly > milestone) was suitable for production and that our actual releases > X.Y.Z.v20170814 looked too like a timestamp and they thought it was some > sort of maven snapshot. I don't even want to think what people think RC# > means. Personally I don't see how this sort of confusion is possible, but > I saw you folks messing around with osgi versioning and figured I would > chime in with some advice to keep it as simple as possible and as much as > possible remove any doubt as to what stage of development an artifact is. > Anything outside of the normal X.Y.Z and people seem to get easily confused.
For a decade, we have released packages with milestones and release candidates... What I see is that people always use the latest version, be it a RC or a M, and as we haven't released a final version of ApacheDS for more than 7 years (yeah, pretty bad, isn'tit ? ;/), I don't think it would make a lot of difference to drop all those RC/M stuff. I was convinced that going for M and RC was teh roght move, but now it seems a bit old fashionned, with project like Vhrome or FF releasing new version every now and then. I do think we might also want to stop releasing M and RC and switch to something simpler, as suggested (ie, x.y.z, period). That's more than enough. However, I would suggest doing so for new releases that don't have *yet* any release, like LDAP API. Ie, LDAP API 2.0.0 would be the next release, because we only have a 1.0.0, but ApacheDS is already using 2.0.0-XXX for years, so it's hard to go for a 2.0.0, because it would break some code (see later comment). For a post 2.0.0.GA ApacheDS release, I'd suggest to go for 3.0.0 and to drop any M and RC (or AM and CR...) > > And avoid P2 repositories unless you have some arcane requirement. Sadly, we can't : Studio is eclipse based, and heavily depends on p2. Thanks for the insights, Jesse. -- Emmanuel Lecharny Symas.com directory.apache.org
