[nvda] Re: What should the next version number be?
- From: Ravi Paul <ravipaul.rp@xxxxxxxxx>
- To: nvda@xxxxxxxxxxxxx
- Date: Tue, 28 Jul 2009 15:23:32 +0530
Hi, although I don't want to go away from the topic, is there a tentitive deadline for the next stable release in the near future? Asking as this topic seems to be discussed so much these days Regards Ravi Paul On 7/28/09, James Teh <jamie@xxxxxxxxxxx> wrote: > On 28/07/2009 7:05 PM, Ravi Paul wrote: >> The problem with basing the version numbering on year though, is, that >> people may get confused about the feature ritch nature of a software >> or the lack of it. >> I think, the whole point of a version number is to make people >> understand the level up to which a software has progressed. > > The problem with that approach is that people place far too much > emphasis on particular numbers, especially when it comes to screen > readers for some reason. Once we hit 1.0, many people will be > disappointed that NVDA got to 1.0 without features x, y or z, despite > the fact that NVDA 1.0 might be more advanced than version 1.0 of a > given competitor product. > > At present, Mick and I are probably somewhere between 0.7 and 2009.1, > leaning perhaps more towards the latter due to its liberating nature; > i.e. it gets us away from expectations of what people think a given > version should have. Having said that, we're still waiting to solicit > more feedback before we make a final decision. > > Jamie > > -- > James Teh > Email/MSN Messenger/Jabber: jamie@xxxxxxxxxxx > Web site: http://www.jantrid.net/ > 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
- References:
- [nvda] What should the next version number be?
- From: Michael Curran
- [nvda] Re: What should the next version number be?
- From: Mike Bledig
- [nvda] Re: What should the next version number be?
- From: Brian's mail list account
- [nvda] Re: What should the next version number be?
- From: Vince Thacker
- [nvda] Re: What should the next version number be?
- From: Brian's mail list account
- [nvda] Re: What should the next version number be?
- From: Ravi Paul
- [nvda] Re: What should the next version number be?
- From: James Teh
- [nvda] What should the next version number be?
Other related posts:
- » [nvda] What should the next version number be? - Michael Curran
- » [nvda] Re: What should the next version number be? - Michel Such
- » [nvda] Re: What should the next version number be? - Felix Grützmacher
- » [nvda] Re: What should the next version number be? - Mike Bledig
- » [nvda] Re: What should the next version number be? - Brian's mail list account
- » [nvda] Re: What should the next version number be? - Brian's mail list account
- » [nvda] Re: What should the next version number be? - Kevin Cussick
- » [nvda] Re: What should the next version number be? - kendell clark
- » [nvda] Re: What should the next version number be? - Simon Jaeger \(laptop\)
- » [nvda] Re: What should the next version number be? - Brian Gaff Lineone downstairs
- » [nvda] Re: What should the next version number be? - José Manuel Ramos
- » [nvda] Re: What should the next version number be? - Brian Gaff Lineone downstairs
- » [nvda] Re: What should the next version number be? - shaun everiss
- » [nvda] Re: What should the next version number be? - shaun everiss
- » [nvda] Re: What should the next version number be? - Vince Thacker
- » [nvda] Re: What should the next version number be? - Ravi Paul
- » [nvda] Re: What should the next version number be? - Brian's mail list account
- » [nvda] Re: What should the next version number be? - Ravi Paul
- » [nvda] Re: What should the next version number be? - Simon Jaeger \(laptop\)
- » [nvda] Re: What should the next version number be? - James Teh
- » [nvda] Re: What should the next version number be? - Ravi Paul
- » [nvda] Re: What should the next version number be? - Brian's mail list account
- » [nvda] Re: What should the next version number be? - Kennydog
- » [nvda] Re: What should the next version number be? - Brian's mail list account
- » [nvda] Re: What should the next version number be? - Nimer Jaber
- » [nvda] Re: What should the next version number be? - Brian Gaff Lineone downstairs
- » [nvda] Re: What should the next version number be? - Nimer Jaber
- » [nvda] Re: What should the next version number be? - Timothy
- » [nvda] Re: What should the next version number be? - Trenton Matthews
- » [nvda] Re: What should the next version number be? - Nimer Jaber
- » [nvda] Re: What should the next version number be? - Brian Gaff
- » [nvda] Re: What should the next version number be? - Trenton Matthews
- » [nvda] Re: What should the next version number be? - Timothy
- » [nvda] Re: What should the next version number be? - Trenton Matthews
- » [nvda] Re: What should the next version number be? - Nimer Jaber