I know it feels way too early, but it's actually getting to be relatively late to talk about planning the Nitrogen release. I know the last few releases, we've talked about making pretty substantial changes and just ran out of steam to implement them.
This time, I'm going to propose something slightly different. Why don't we try one or two more minor changes. The two relatively simple changes that come to my mind first are: 1.) Moving to having a common version range for each artifact rather than a common version. That is moving from x.y.z-SNAPSHOT to x.y.[z,z+1) or maybe even x.[y,y+1) and then have merge jobs publish both SNAPSHOT as well as release artifacts with a build number as fourth part of the version. I'm sure that there are details I'm glossing over (and I know of a few), but it would be a relatively simple step toward decoupling some of our release process. Some information on this is in an old thread here too: https://lists.opendaylight.org/pipermail/tsc/2016-July/005536.html 2.) Moving to a twice a year release process. This would help planning by not having our release dates shift randomly around each year, fall more in line with other open source projects, get us cycling a bit faster, and maybe also have some more discipline. I talked about it a bit before here: https://lists.opendaylight.org/pipermail/tsc/2016-July/005665.html Please chime in with any thoughts. Cheers, --Colin
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
