I do not in principle have any objection, but think you should detail a little more about what's new, that caused the "minor" increase.
Just a few new API? That are fully backwards compatible? Or some wildly new features? Did a lot of your bundles/packages increase their minor version? Or just a few? Or, were new bundles simply added? Also, I think knowing just how much of a "leaf" this is would help. Is there any projects in Simultaneous release repo that make use of it? If so, I think it would be helpful to know, in parallel, if that version "currently aggregates ok". You can determine this either directly in b3 aggregator editor (via "validation") or use a Gerrit job to validate, without checking in the contribution yet. To explain, the risk in cases like this, even when new API is backwards compatible, is if someone was using something "internal" and had a narrow range specification, such as [2.0.0, 2.1.0) since if they did, those projects or adopters would then have to change their code ... at least the version range. Also, has this been announced on your 'dev list'? Are the changes something requested by adopters? Any bug numbers that explain the "minor" increase? I am asking these questions, partially, to make it clear that while we want rapid improvements we don't want to foster a "wild west" culture where projects "do what they want, even if harmful to others". I suspect in your case there's nothing (or, little risk) of doing anything harmful, but answers to the questions above would help all of us be able to assess that better. Thanks, From: Tom Schindl <[email protected]> To: [email protected], Date: 08/21/2015 04:47 AM Subject: Re: [cross-project-issues-dev] Staging repos are complete for Mars.1 RC1 and Neon M1 Sent by: [email protected] [...] > For maintenance, we do not have another place to put RC candidates, but > will wait until official release to move to ../releases/mars. In the > mean time, please test directly from .../releases/maintenance. Because I did not have any feedback from my PMC I did not contribute the 2.1.0 version of e(fx)clipse to the maintenance release. Is it still possible to contribute to 2.1.0 for RC2. The release has been scheduled by Wayne now for Sep. 2nd. Tom -- Thomas Schindl, CTO BestSolution.at EDV Systemhaus GmbH Eduard-Bodem-Gasse 5-7, A-6020 Innsbruck http://www.bestsolution.at/ Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck _______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
