We have differing visions of what "Jenkins 2.0" would actually mean, and those visions are to a certain extent mutually incompatible - getting 2.0 out in the timeframe Kohsuke has proposed wouldn't be possible if that requires not just the user experience work he has mentioned but also storage changes, a jenkins configuration API, etc... So I have my own proposal: break the work into a few tracks, each overseen by a shepherd, on different schedules. So the initial 2.0 release would be the work Kobsuke has put forward, but at the same time, another set of devs will be working on the initial storage changes, targeting 2.15 or something like that.
Since the Big Bang model with significant comparability breaking changes is not a viable option, these tracks will still need to be concerned with backwards compatibility for existing jobs, plugins and build history, as well as working with the tracks scheduled to be released earlier, but this will allow us to make bigger, longer-term plans than we have previously. Kohsuke's 2.0 proposal gives us the blueprint for this - define a scope, define a goal timeline, implement the changes, verify compatibility and stability, and then release. We can follow this model for significant work going forward, not just now. Having a designated person serving as a shepherd will give us someone who is focused on defining the scope and making sure the work gets done. Let's aim at having three tracks going at a time as a max - we need to focus the development efforts to be sure we complete them! My initial proposal would look something like this: - 2.0 track - As Kohsuke has laid out. Shepherded by Kohsuke. Release planned for February 2016 (I like to cushion schedules a bit to make sure they're not just aspirational but actually realistic - given the breadth of front end changes discussed, this may be an overly aggressive date). - Pluggable storage/database backend - Scope to be determined, myself as shepherd, target release date of April 2016. - ? For the third track, let's try to reach a consensus on what the next priority should be. It could be stability, it could be plugin cleanup (too many plugins!), it could be configurability and platform (I.e., config API, Java 8, etc). Thoughts? 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/CAPbPdOY4vJ0XzEFO19qjh9Ha4h8GAcj-P4H-0KVs%3Dr9888p2cw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
