On 01/07/2016 03:35 PM, Remi Bergsma wrote: > > We released: > 4.6.0 > 4.6.1 > 4.6.2 > 4.7.0 > (4.7.1) > (4.8.0) > > We _do_ release minor releases, and every month one with new features. > > To be clear: > Any branch (be it 4.5, 4.6, 4.7) can have as many minor releases as people > want, until the end of time. Just step up and release it. >
And that is indeed it. I'm not keen on doing point releases either. Simplify upgrade paths, ditch the fact that a VR has to be upgraded every time, etc, etc. We could also call 4.8 simply 4.7.2. It's just a number :) Wido > Regards, > > Remi > > > > >> We are not yet on 4.6, so we have downtime by upgrading the routers, we >> have approx 120 VR, which take about ~ 5-10 minutes of downtime each. >> >> We are not agile in upgrading, we have freeze times and plan our >> releases and test each release intensively (it saved our asses in the past). >> >> Every bigger software project in the world has agreed that providing >> minor releases is good practice: >> >> - New features --> Major release >> - Fixes --> Minor release >> >> The problem with new features are potentially new bugs (by nature): >> >> Now you are basically saying: >> >> - New features and fixes --> Major release only >> >> By definition, you will end up it a more unstable software because you >> will only get fixes in cost of new features and potentially new bugs. I >> don't call this stable. >> >> I do not see any benefit of the current release rush. >> >> René
