[nvda] Re: What should the next version number be?

The linux man couldn't  have said it better...
I say go with his idea!


On 7/29/09, Brian Gaff <bglists@xxxxxxxxxxxxxxxx> wrote:
> Now why didn't I think of that.. Sounds too logical though... grin.
>
> Brian
>
> This account only receives email from the list. Please direct any personal
> email to
> briang1@xxxxxxxxxxxxxxxx
> Replies to this address vanish into a hole....
> Unless Brian Gaff is in the To line display name field.
> ----- Original Message -----
> From: "Nimer Jaber" <nimerjaber1@xxxxxxxxx>
> To: <nvda@xxxxxxxxxxxxx>
> Sent: Wednesday, July 29, 2009 4:32 AM
> Subject: [nvda] Re: What should the next version number be?
>
>
>>I have a problem with this idea. The problem is tat when do we or the
>> NVDA team determine when NVDA reaches versionone? I mean, NVDA has
>> developed many new concepts that are beyond many of the commercial
>> screen readers were at version one, and the NVDA team continues to
>> make big strides in terms of accessibility. I propose that we call the
>> NVD versions similar to how different versions of Linux operate.
>> Year/month. So, if NVDA was released this month, it would be called
>> NVDA 2009.7 and any subsequent version would be numerically higher,
>> 2009.7.2, signifying that this was the second version released in tghe
>> month of July in 2009.
>>
>> Thanks
>> Nimer J
>>
>> On 7/28/09, Trenton Matthews <trenton.tmantv@xxxxxxxxx> wrote:
>>> Here's my take on the matter:
>>>
>>> Wikipedia still classifies NVDA, as "alpha" software.
>>> I personally go with 0.70 "beta," That way, no one gets confused with
>>> Windows 7, and no one thinks its a 7.0 release.
>>> And also, folks at wikipedia can't say its just alpha software.
>>> This idea came to me while reading older skype versions,  as before
>>> they were 1.0, they all had "beta" after their number.
>>>
>>> So, until NVDA hits that 1.0 mark, I consider NVDA, as "beta" software.
>>> That's my thoughts, hope you enjoyed reading.
>>>
>>> Good day.
>>>
>>> Trenton
>>> An
>>>
>>> On 7/28/09, Timothy <tmthywynn8@xxxxxxx> wrote:
>>>> 0.6 would be fine with me. As for the preview releases, you should be
>>>> naming
>>>> it beta since it's more common. 0.6 beta 3 would make more sense. So
>>>> when
>>>> the actual 0.6 comes out, no one would be confused.
>>>>
>>>> 0.7 would als make sense since we made so many different
>>>> changes/enhancements. Braille displayes, navigation keys, links list,
>>>> heading lists, form lists, etc.
>>>>
>>>> ----- Original Message -----
>>>> From: "shaun everiss" <shaun.e@xxxxxxxxxx>
>>>> To: <nvda@xxxxxxxxxxxxx>
>>>> Sent: Monday, July 27, 2009 8:02 PM
>>>> Subject: [nvda] Re: What should the next version number be?
>>>>
>>>>
>>>> hi mike and all the nvda devs.
>>>> 0.6.5 would work.
>>>> as with the preview release, I have seen in the opensource software
>>>> place
>>>> release candidate releases so instead of 0.6p1 0.6rc1 or just nvda rc1,
>>>> or
>>>> whatever.
>>>> ANother thing we could do is have things defined like 0.6 beta.
>>>> Another thing we could use is build numbers, like 0.6.204 or
>>>> 0.6.2009.1.14
>>>> or something although some I spoke to loath that system.
>>>> going to 0.7 and missing out 6 could be good although its always been my
>>>> understanding that everyone is expecting 0.6.
>>>> winlame another project I used switched to the 2009.1 version, although
>>>> they
>>>> did put a beta number on it.
>>>> 1.0 hmmm may be a bit to close for that one.
>>>> as you say its not stable.
>>>> 1.0 beta# where # is the number, I suppose would work although you would
>>>> get
>>>> then loads of betas.
>>>> You could use the build numbers from the last snapshot the stuff was
>>>> compiled from, ie .0.6 build 2300.
>>>> At 10:24 p.m. 27/07/2009, you wrote:
>>>>>Hi all,
>>>>>
>>>>>Please have a read of the blog post:
>>>>>http://www.nvda-project.org/blog/WhatShouldNextVersionNumberBe
>>>>>
>>>>>And provide any feedback you can.
>>>>>
>>>>>Thanks
>>>>>Mick
>>>>>To post messages to the list send email to
>>>>>nvda@xxxxxxxxxxxxx
>>>>>To modify your NVDA Email settings go to:
>>>>>http://www.freelists.org/list/nvda
>>>>>Thank you for your continued support of Nonvisual Desktop Access, an
>>>>>open
>>>>>source free screen reader for Microsoft Windows:
>>>>>http://www.nvda-project.org/
>>>>>To get the latest NVDA snapshot:
>>>>>http://www.nvda-project.org/snapshots/
>>>>>Report bugs or make feature requests at:
>>>>>http://trac.nvda-project.org/
>>>>>Message Archive:
>>>>>http://www.freelists.org/archives/nvda
>>>>
>>>>
>>>> To post messages to the list send email to
>>>> nvda@xxxxxxxxxxxxx
>>>> To modify your NVDA Email settings go to:
>>>> http://www.freelists.org/list/nvda
>>>> Thank you for your continued support of Nonvisual Desktop Access, an
>>>> open
>>>> source free screen reader for Microsoft Windows:
>>>> http://www.nvda-project.org/
>>>> To get the latest NVDA snapshot:
>>>> http://www.nvda-project.org/snapshots/
>>>> Report bugs or make feature requests at:
>>>> http://trac.nvda-project.org/
>>>> Message Archive:
>>>> http://www.freelists.org/archives/nvda
>>>>
>>>> To post messages to the list send email to
>>>> nvda@xxxxxxxxxxxxx
>>>> To modify your NVDA Email settings go to:
>>>> http://www.freelists.org/list/nvda
>>>> Thank you for your continued support of Nonvisual Desktop Access, an
>>>> open
>>>> source free screen reader for Microsoft Windows:
>>>> http://www.nvda-project.org/
>>>> To get the latest NVDA snapshot:
>>>> http://www.nvda-project.org/snapshots/
>>>> Report bugs or make feature requests at:
>>>> http://trac.nvda-project.org/
>>>> Message Archive:
>>>> http://www.freelists.org/archives/nvda
>>>>
>>> To post messages to the list send email to
>>> nvda@xxxxxxxxxxxxx
>>> To modify your NVDA Email settings go to:
>>> http://www.freelists.org/list/nvda
>>> Thank you for your continued support of Nonvisual Desktop Access, an open
>>> source free screen reader for Microsoft Windows:
>>> http://www.nvda-project.org/
>>> To get the latest NVDA snapshot:
>>> http://www.nvda-project.org/snapshots/
>>> Report bugs or make feature requests at:
>>> http://trac.nvda-project.org/
>>> Message Archive:
>>> http://www.freelists.org/archives/nvda
>>>
>> To post messages to the list send email to
>> nvda@xxxxxxxxxxxxx
>> To modify your NVDA Email settings go to:
>> http://www.freelists.org/list/nvda
>> Thank you for your continued support of Nonvisual Desktop Access, an open
>> source free screen reader for Microsoft Windows:
>> http://www.nvda-project.org/
>> To get the latest NVDA snapshot:
>> http://www.nvda-project.org/snapshots/
>> Report bugs or make feature requests at:
>> http://trac.nvda-project.org/
>> Message Archive:
>> http://www.freelists.org/archives/nvda
>>
>
>
> --------------------------------------------------------------------------------
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.392 / Virus Database: 270.13.29/2261 - Release Date: 07/25/09
> 05:58:00
>
>
> To post messages to the list send email to
> nvda@xxxxxxxxxxxxx
> To modify your NVDA Email settings go to:
> http://www.freelists.org/list/nvda
> Thank you for your continued support of Nonvisual Desktop Access, an open
> source free screen reader for Microsoft Windows:
> http://www.nvda-project.org/
> To get the latest NVDA snapshot:
> http://www.nvda-project.org/snapshots/
> Report bugs or make feature requests at:
> http://trac.nvda-project.org/
> Message Archive:
> http://www.freelists.org/archives/nvda
>
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To modify your NVDA Email settings go to:
http://www.freelists.org/list/nvda
Thank you for your continued support of Nonvisual Desktop Access, an open 
source free screen reader for Microsoft Windows:
http://www.nvda-project.org/
To get the latest NVDA snapshot:
http://www.nvda-project.org/snapshots/
Report bugs or make feature requests at:
http://trac.nvda-project.org/
Message Archive:
http://www.freelists.org/archives/nvda

Other related posts: