[nvda] Re: What should the next version number be?
- From: "Brian's mail list account" <bglists@xxxxxxxxxxxxxxxx>
- To: <nvda@xxxxxxxxxxxxx>
- Date: Tue, 28 Jul 2009 09:45:54 +0100
I still favour the year. It is what it says on the tin, so to speak, no need to look yp which is the latest, you would know pretty well which year it was built.
Brian bglists@xxxxxxxxxxxxxxxx Sent via blueyonder. Please address personal email to:- briang1@xxxxxxxxxxxxxxxx, putting 'Brian Gaff' in the display name field.----- Original Message ----- From: "Vince Thacker" <vince@xxxxxxxxxxxxxxxxxxxxx>
To: <nvda@xxxxxxxxxxxxx> Sent: Tuesday, July 28, 2009 4:28 AM Subject: [nvda] Re: What should the next version number be?
You could always establish a Department for Silly Names, like the people who brought you Longhorn and Vista. So you could have NVDA <Moonwalker, followed by NVDA SunTrkker, follwed by....um, freedom rider.... Oh, no, someone mightsue you. I wouldn't like to say who that might be. Hmm, you've also got to worry about what the name means in 65 other languages. Remember the Rolls-Royce Silver Mist? Ok, back to the drawing board. Vince.----- Original Message ----- From: "Brian's mail list account" <bglists@xxxxxxxxxxxxxxxx>To: <nvda@xxxxxxxxxxxxx> Sent: Monday, July 27, 2009 5:46 PM Subject: [nvda] Re: What should the next version number be?No, but its not snazzy enough to convince people to try it out is it? grin. people like easy, easy is the year, in my view. Notice on for example, File Hippo, you get given new versions of software served up to you, and any beta ones. A nice name makes it clear what it is, so people tell me. Not that I'm suggesting allowing file hippo to have it, but then again... Brian bglists@xxxxxxxxxxxxxxxx Sent via blueyonder. Please address personal email to:- briang1@xxxxxxxxxxxxxxxx, putting 'Brian Gaff' in the display name field.----- Original Message ----- From: "Mike Bledig" <mgbledig@xxxxxxxxxxxxxx>To: <nvda@xxxxxxxxxxxxx> Sent: Monday, July 27, 2009 4:19 PM Subject: [nvda] Re: What should the next version number be?Hi there, I think the current versioning system is ok, but just needs to be made a little more clear. so in other words, version nvda_0.6p3.2_installer could be stated as nvda_rel0.6pre3.2_installer.So reading it one would know: it's a release of 0.6 of a preview at stage3 with a miner repair at that stage Its not that difficult to follow if you really think about it. Kind regards, Mike -----Original Message----- From: nvda-bounce@xxxxxxxxxxxxx [mailto:nvda-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Curran Sent: Monday, July 27, 2009 12:25 PM To: nvda@xxxxxxxxxxxxx; Development for NonVisual Desktop Access Subject: [nvda] What should the next version number be? 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/nvdaThank you for your continued support of Nonvisual Desktop Access, an opensource 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/nvdaThank you for your continued support of Nonvisual Desktop Access, an opensource 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.comVersion: 8.5.392 / Virus Database: 270.13.32/2266 - Release Date: 07/27/0905: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/nvdaTo post messages to the list send email to nvda@xxxxxxxxxxxxx To modify your NVDA Email settings go to: http://www.freelists.org/list/nvdaThank 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.comVersion: 8.5.392 / Virus Database: 270.13.32/2266 - Release Date: 07/27/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
- Follow-Ups:
- [nvda] Re: What should the next version number be?
- From: Ravi Paul
- [nvda] Re: What should the next version number be?
- 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] 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