+1 #2
On Wed, Sep 4, 2013 at 3:24 AM, Joe Bowser <[email protected]> wrote: > +1 for #2 > > On Tue, Sep 3, 2013 at 11:38 AM, Anis KADRI <[email protected]> wrote: > > +1 for number 2 > > > > On Tue, Sep 3, 2013 at 10:16 AM, David Kemp <[email protected]> wrote: > >> +1 for #2 as well > >> > >> > >> On Tue, Sep 3, 2013 at 1:10 PM, Braden Shepherdson <[email protected] > >wrote: > >> > >>> +1 for #2. > >>> > >>> > >>> On Tue, Sep 3, 2013 at 12:55 PM, Michal Mocny <[email protected]> > wrote: > >>> > >>> > +1 for option #2 > >>> > > >>> > > >>> > On Tue, Sep 3, 2013 at 12:21 PM, Andrew Grieve <[email protected] > > > >>> > wrote: > >>> > > >>> > > For repos that use SemVer, there are two options: > >>> > > > >>> > > 1. Update the version number at the time that the change is made > >>> > > 2. Update the version number only when doing a release. > >>> > > > >>> > > Right now, #2 is what I've put in the wiki instructions, but it > can be > >>> > > changed of course :) > >>> > > > >>> > > Two main reasons I think #2 will work better: > >>> > > - #1 might be too complicated (might forget to update it, may > update > >>> the > >>> > > version multiple times if multiple feature changes go in) > >>> > > - #2 If doing a release, you should know what you're releasing. > Having > >>> > to > >>> > > choose the right version number will force you to understand what > >>> you're > >>> > > releasing. > >>> > > > >>> > > >>> >
