On Thu, Oct 8, 2015 at 11:12 AM, Vojtech Juranek <[email protected]> wrote:
> in general I agree with your (I'd like to see changes in backend happen as > well), but I'm not sure about this one - you don't expect any API changes > or > you propose to do backward incompatible changes in a minor version change? > If > the former, IMHO it doesn't need to be bind to 2.0, just form group of > interested devs and make the change, if later it seems to me quite > unfortunate > to do any incompatibility changes during minor version bump. IMHO lots of > people expect, if not state clearly otherwise, that any backward > incompatible > changes happen only during major version bump. > Yeah, the former - unless we as a community decide to change our philosophy on backwards incompatible changes, 2.0 or otherwise, we're pretty much stuck maintaining existing APIs forever. And no, it's not bound to 2.0 - I just think the confusion over what 2.0 would mean and the desire to get bigger changes in shows we need to work on longer-term changes deliberately, as a group. 2.0 (in Kohsuke's vision) is one set of thematically connected longer-term changes, pluggable storage backend is another, etc. > With 2.0 bump discussion, IMHO it would be useful if we define what major > version bump exactly means for Jenkins (i.e. still very limited backward > incompatible changes; only some API changes - only plugin maintainers > should > take care; backward incompatible changes can happen - every admin should > take > care and look if some config migration is needed; etc) and also how often > we > expect major version changes. If cca once a year (or e.g. once some major > feature is developed and tested), IMHO it's fine to wait with it for 3.0, > if > we stick with 2.0 for another 10 years, than makes sense for me to postpone > 2.0 and implement more changes. > Last night/morning (time zones!) at the office hours, I tossed out the idea of changing our numbering - to 2.0.x, 2.1.x, etc, to give us the opportunity to make more drastic/compatibility-related changes before a distant 3.0. Kohsuke was not enthused. =) He'd like to stay on the same model as 1.x for versioning. A. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPbPdOZwwQxAtg0GdaAKiue92aXxqPOuqvii1k_MO1zo3SuUng%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
