Fw: [Nvda-devel] How the branches work at new version time and after


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

Thought this might be handy for new folk.
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: "Michael Curran" <mick@nvaccess.org>
To: "NVDA screen reader development" <nvda-devel@lists.sourceforge.net>
Cc: "Brian's Mail list account BY" <bglists@blueyonder.co.uk>
Sent: Monday, September 10, 2018 10:06 PM
Subject: Re: [Nvda-devel] How the branches work at new version time and after


Beta goes to rc and then to stable.

Once a beta comes out for 2018.4, users will need to manually download the new beta.


Mick


On 11/09/2018 5:49 am, Brian's Mail list account BY via Nvda-devel wrote:
OK seen the bit about the RC early this morning and updated my RC portable, but later in the day, the installed beta version also updated to the rc version.
Is this what is supposed to happen?
Question, so what happens when the stable version immerge, does the beta version update to the stable or carry on as the beta and the stable has to be downloaded or updated via the current stable portable or installed version?

Did that question make sense?

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.


_______________________________________________
Nvda-devel mailing list
Nvda-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nvda-devel

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