[wp-hackers] Plugin Version Increments

[Viper007Bond]

That's how I do it as well. No even or odd stuff.

First = complete recode edition or at least huge changes
Second = new features or whatnot, but not crazy big code wise
Third = bugfixes

On Sat, May 3, 2008 at 8:03 AM, <nick at ohrnventures.com> wrote:

> I'm not sure if there is an industry standard, but this is the way I do
> it:
>
> If I am fixing typos, small bugs, or correcting an error that happens in a
> small number of configurations, I iterate the third number.
>
> If I am adding features but not breaking the way any current functionality
> works, I iterate the second number.
>
> If I'm adding more than 2 features and backward compatibility might be
> broken, I iterate the first number.
>
> A script is released < 1.0 if the author considers it "beta" and not
> completely finished.
>
> Best,
> Nick Ohrn
>
> > 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
>



-- 
Viper007Bond | http://www.viper007bond.com/ | http://www.finalgear.com/