[wp-hackers] Plugin Version Increments

[Ryan McCue]

Alexander Beutl wrote:
> Because they added so much stuff that everything was broken afterwards ;-)
> just kidding but there were many changes and additions - (just think about
> the admin interface, the swf uploader, the gallery functionality, the
> shortcodes,...) that someone decided this are too many changes for a single
> subversion jump while there are not many enogh for a mayer version jump.
>
> 2008/5/3 Glenn Ansley <glenn at glennansley.com>:
>
>   
>> Thanks these responses were helpful.
>> BTW, why did WP skip 2.4?
>>
>> On Sat, May 3, 2008 at 11:35 AM, Viper007Bond <viper at viper007bond.com>
>> wrote:
>>
>>     
>>> 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/
>>> _______________________________________________
>>> 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
>>
>>     
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>   
No, they skipped it because the release date was going to be during the 
Christmas period, which, combined with the fact Ryan Boren had some sort 
of illness, would have meant that they wouldn't be able to fit 
everything they wanted to in.
Also, they knew that the admin panel redesign couldn't be finished in 
time. They could have delayed the release, but this would have thrown 
the rest of the release timeline out.

Thanks,
Ryan.