From: Dmitriy S. <sha...@gm...> - 2013-03-26 15:44:12
|
Than stable branch should be 2.0.x, next developing version 2.1.x and next stable 2.2.x and so on ... right? We will continue increment minor till new *very* cool feature will be planned or better ready for release. At that time 2.some-odd will be released as 3.0.x. On Tue, Mar 26, 2013 at 4:17 PM, Adam Retter <ad...@ex...> wrote: > Nope I am describing major.minor.maintenance > > On 26 March 2013 11:14, Dmitriy Shabanov <sha...@gm...> wrote: > > you describe major.minor versioning, right? > > > > On Tue, Mar 26, 2013 at 4:04 PM, Adam Retter <ad...@ex...> wrote: > >> > >> Erm my thought was more like this - > >> > >> 2 is done. We want to work on new major changes right? So major > >> changes mean version 3. > >> > >> We have a 2.x stable branch - this is effectively where we merge in > >> new small/incremental features (minor revisions) and bugfixes > >> (maintenance revisions). From the 2.x branch we can then make releases > >> which will be either minor or maintenance releases. > -- Dmitriy Shabanov |