Re: New release system and new snapshot names from Mick


Brian's Mail list account <bglists@...>
 

I'm not saying they are wrong in their idea, merely that we have a problem since people have been able to treat master as a beta for some years now, and what is needed is some way to flag this change to those not often on here but who do come on when things go wrong. My work around ideas were just that. As long as when the change is made a simple way out I of it is given, then fine. I do know of a couple of people on this list from time to time who use master in a company, installed by admin so they can have the latest stable at all times, but these people will need to contact their admins in order to put them on the new beta channel. One assumes that master will be ported to that channel for the time being so that people can still have a working version.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Kevin Cussick via Groups.Io" <the.big.white.shepherd=googlemail.com@groups.io>
To: <nvda@nvda.groups.io>
Sent: Wednesday, July 04, 2018 10:15 PM
Subject: Re: [nvda] New release system and new snapshot names from Mick


well, after reading about this I think I agree with the devs. I am also pleased to see Nvda improving the way it is being updated. I would hope that most people who run master or the new beta are aware that things may not work as expected.

On 04/07/2018 07:36, Brian's Mail list account via Groups.I wrote:
From: "Mick Curran" <mick@nvaccess.org>
To: "NVDA screen reader development" <nvda-devel@lists.sourceforge.net>;
<nvda-translations@groups.io>
Sent: Wednesday, July 04, 2018 2:43 AM
Subject: [Nvda-devel] Changes to release process


Hi contributors,


We have made some small changes to the NVDA release process. Please read
the updated Release Process article carefully to understand the changes
and how they will affect you.

https://github.com/nvaccess/nvda/wiki/ReleaseProcess


In short, Next/incubation is going away, and prs are going to be merged
straight to master. Periodic betas will be offered startin from 5 weeks
before a release.

Please read the entire article to understand the changes fully.


Translators should not be directly affected by this change. Though
technically, translations are now based on a new "beta" branch rather than
master.


Mick









--
--
Mick Curran
Executive Director, NV Access Limited
PH: +61 7 3149 3306 ext. 101
www: http://www.nvaccess.org/
Twitter: @NVAccess
Facebook: http://www.facebook.com/NVAccess


------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Brian comments. I think this is actually going to affect people on this list
like myself who use the bleeding edge code as portable versions and master
as a daily working version.
I worry a little hear about a large number of untested by users items
arriving in the beta all at once which might be a little scary if a lot of
people find issues. At the moment they hit next regularly and one can see
the wood for the trees so to speak.

If you have any comments, send them to Mick not me though, as I do not see
any kind of consultation with users on this one.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.


Join nvda@nvda.groups.io to automatically receive all group messages.