Re: [Nvda-devel] New release process

[Mesar H. <mes...@gm...>]

Hi,

If you are running a release version, it will act as usual and update
only whenever a new release is made available.

If you are running a master branch snapshot, it is similar to running
Continuous beta code. i.e. the latest changes has been had some limited
testing and may still cause problems, but the obvious issues should have
been ironed out. 
If you are running a snapshot from 'next' branch, it is the same as
running bleeding edge snapshots, i.e. you parttaking in active bug
hunting and you are acting as the first line of serious user checking
for bugs and you are willing to actively report any oddities.

Hope this clarifies somewhat.
Thanks
Mesar
On Thu 27/06/13,13:34, Homme, James wrote:
> Hi,
> The blog post sounds like you can choose how you get NVDA updates. How does that differ from allowing NVDA to check for updates? At home, before this change, I was allowing NVDA to get updates of snapshots, then we got Git. Now, when NVDA asks for me to update it, it's talking about Master and has a couple of different numbers that I don't understand. I just trust that I'm getting a snapshot. So basically, I'm confused, which happens easily. At work, it seems like NVDA is only looking for updates when a major release happens, or a bug fix of a major release happens. Is the way to control that to go and start getting snapshots? Sorry for the confusion.
> 
> Jim
> 
> 
> -----Original Message-----
> From: James Teh [mailto:ja...@nv...]
> Sent: Thursday, June 27, 2013 1:13 AM
> To: NVDA development mailing list
> Subject: [Nvda-devel] New release process
> 
> Hi all,
> 
> There have been some changes in the way we will be making development and beta code available to the wider community for testing. This is mostly to ensure that new features get the widest amount of testing possible, while at the same time ensuring that we have a codebase of NVDA which is at or near release quality at all times. This will facilitate a faster, smoother release process.
> 
> Please see this post for details:
> http://community.nvda-project.org/blog/NewReleaseProcess
> 
> Thanks,
> Jamie
> 
> --
> James Teh
> Director, NV Access Limited
> Ph + 61 7 5667 8372
> www.nvaccess.org
> Facebook: http://www.facebook.com/NVAccess
> Twitter: @nvaccess
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Nvda-devel mailing list
> Nvd...@li...
> https://lists.sourceforge.net/lists/listinfo/nvda-devel
> 
> ________________________________
> 
> This e-mail and any attachments to it are confidential and are intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this e-mail without the author's prior permission. The views expressed in this e-mail message do not necessarily represent the views of Highmark, its diversified business, or affiliates.
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Nvda-devel mailing list
> Nvd...@li...
> https://lists.sourceforge.net/lists/listinfo/nvda-devel