It is currently September 21st, 2021, 4:35 pm

4.5.1.3538

Test and provide feedback on potential changes
User avatar
death.crafter
Posts: 937
Joined: April 24th, 2021, 8:13 pm

Re: 4.5.1.3538

Post by death.crafter »

jsmorley wrote: September 12th, 2021, 10:05 am Agreed. This was my bad. What we will go going forward is have say release 4.5.2.3600, then prerelease 4.5.2.3700, which will end up as release 4.5.3.3700. In any case, yes, prerelease versions should prompt for upgrade when the release version is out.
What I had in mind was more like, you release 4.5.2.3600, then go forward with prerelease versions 4.5.3.36xx, the make a final release of 4.5.3.3700.

Again move forward with 4.5.4.37xx and then release 4.5.4.3800.

This way, prerelease versions can get the updates for finals too, without any workarounds. And ofc, a check box for getting notice for prereleases.
from the Realm of Death
My Current Desktop
User avatar
jsmorley
Developer
Posts: 22288
Joined: April 19th, 2009, 11:02 pm
Location: Fort Hunt, Virginia, USA

Re: 4.5.1.3538

Post by jsmorley »

death.crafter wrote: September 12th, 2021, 10:33 am What I had in mind was more like, you release 4.5.2.3600, then go forward with prerelease versions 4.5.3.36xx, the make a final release of 4.5.3.3700.

Again move forward with 4.5.4.37xx and then release 4.5.4.3800.

This way, prerelease versions can get the updates for finals too, without any workarounds. And ofc, a check box for getting notice for prereleases.
No, we would prefer not to have prerelease versions be part of the auto-update functionality. When a new actual release is out, they will prompt to get it, but not from one prerelease to another. The prerelease process is intended to be something folks are actively and manually engaged in. Pre-release versions are in no way intended to be widely used by the general public.
User avatar
death.crafter
Posts: 937
Joined: April 24th, 2021, 8:13 pm

Re: 4.5.1.3538

Post by death.crafter »

jsmorley wrote: September 12th, 2021, 10:38 am No, we would prefer not to have prerelease versions be part of the auto-update functionality. When a new actual release is out, they will prompt to get it, but not from one prerelease to another. The prerelease process is intended to be something folks are actively and manually engaged in. Pre-release versions are in no way intended to be widely used by the general public.
Hmm makes sense.
from the Realm of Death
My Current Desktop
User avatar
jsmorley
Developer
Posts: 22288
Joined: April 19th, 2009, 11:02 pm
Location: Fort Hunt, Virginia, USA

Re: 4.5.1.3538

Post by jsmorley »

Alright, thanks to all for helping us test! I think we can leave this thread now. Anything else that comes up with 4.5.2 should be posted in "bugs and feature suggestions", since it is now "released". When we make further changes, we will start a new thread in this area.