[wp-hackers] Plugin Version Increments

Glenn Ansley glenn at glennansley.com
Sat May 3 14:46:42 GMT 2008


>
> the major revisions are consecutive odd
> numbers and the minor are consecutive counting numbers.


So you would go from 1.1 to 1.3 and skip 1.2?

On Sat, May 3, 2008 at 10:38 AM, Aaron Harun <admin at anthologyoi.com> wrote:

> Usually if a script has a version less than 1.0, it is assumed that it
> is still "beta" and may go boom.
>
> Other than that it is up to you. Usually going from 1.0 -> 2.0 signals
> a large change, 1.0 -> 1.5 signals a medium change, 1.0.0 -> 1.0.1 is
> usually something fairly small. It is very arbitrary and usually is
> used however the dev wants to use it, but be consistent within your
> own project. Don't go from 1.0 to 1.1 to 1.2.3 to 1.7 to 3.14.
>
> Right now for one of my larger projects I'm using 1.(major revision
> number).(minor revision). The major revisions are consecutive odd
> numbers and the minor are consecutive counting numbers.
>
>
> On Sat, May 3, 2008 at 10:29 AM, Glenn Ansley <glenn at glennansley.com>
> wrote:
> > Is there any industry or WordPress preferred method for version number
> >  increments?
> >  I've never released code to the public before that had the potential of
> >  future revisions. What determines if a script goes from 1.0 to 1.1 or
> 1.1.1
> >  or 2.0? Also, what determines if the initial script is released < 1.0?
> >
> >  If there is no "standard", why do you do it like you do?
> >
> >  Thanks,
> >  Glenn Ansley
> >  _______________________________________________
> >  wp-hackers mailing list
> >  wp-hackers at lists.automattic.com
> >  http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>


More information about the wp-hackers mailing list