release cycle

If it doesn't fit anywhere else, drop it in here. (not to be used as a chat/nonsense section)

Moderator: Moderator Team

Post Reply
User avatar
Michael Long
Posts: 40
Joined: Wed Oct 25, 2017 7:51 pm

release cycle

Post by Michael Long »

Hello,
I have a newbe question about the release cycle of ReactOS.

I noticed on iso.reactos.org that there are already builds for 0.4.8 even though the official last released version is still 0.4.6. Some days later (yesterday) the first bug was fixed with the fixVersion 0.4.8 (instead of 0.4.7). Wasn't the version 0.4.7 intended for end of November/next month? When can the official 0.4.7-version be expected and will in be a plain copy of the last version available on iso.reactos.org which states "0.4.7" in it's file name?

Thanks.

Regards,
Michael

ctasan
Posts: 385
Joined: Mon Feb 24, 2014 7:02 pm
Location: Istanbul, Turkey
Contact:

Re: release cycle

Post by ctasan »

If there's a 0.4.7-rc1 branch (it is), then expect a release in coming weeks (test period!). 0.4.8 is gonna take another 3 months.
ReactOS Community Changelogs | Admin of ReactOS Turkish Twitter account @reactos_tr

User avatar
DougLyons
Posts: 21
Joined: Sat Oct 25, 2014 9:10 pm
Location: Pensacola, Florida, USA

Re: release cycle

Post by DougLyons »


oldman
Posts: 1128
Joined: Sun Dec 20, 2009 1:23 pm

Re: release cycle

Post by oldman »

Michael Long wrote:I noticed on iso.reactos.org that there are already builds for 0.4.8 even though the official last released version is still 0.4.6. Some days later (yesterday) the first bug was fixed with the fixVersion 0.4.8 (instead of 0.4.7). Wasn't the version 0.4.7 intended for end of November/next month? When can the official 0.4.7-version be expected and will in be a plain copy of the last version available on iso.reactos.org which states "0.4.7" in it's file name?
With the move to Git, the revision number format changed from like this r76032 to like this 0.4.7-dev-701-gb46d3ce5e9, so when they branched for a 0.4.7 release, the version number went up and changed to be like this 0.4.8-dev-19-g840320cbd1. When the 0.4.8 master is branched for the 0.4.8 release, you will see that the number will have moved up again.

Before a release is out, you may see in JIRA, bug fixes with fixed version of 0.4.7 as well as 0.4.8. If the developers think that it should go into the 0.4.7 release, you will see 0.4.7 as the fixed version, else it will have a fixed version of 0.4.8.

When they branch for a release, the branch is worked on to fix as many bugs as possible, to make it a reasonably stable a release. There will still be some bugs in the release, but it will be a more stable version than the actual version it was branched from.
Please keep the Windows classic (9x/2000) look and feel.
The layman's guides to - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.

User avatar
Michael Long
Posts: 40
Joined: Wed Oct 25, 2017 7:51 pm

Re: release cycle

Post by Michael Long »

Thank you.

ElliotMac
Posts: 1
Joined: Thu Nov 09, 2017 11:30 am

Re: release cycle

Post by ElliotMac »

oldman wrote:
Michael Long wrote:I noticed on iso.reactos.org that there are already builds for 0.4.8 even though the official last released version is still 0.4.6. Some days later (yesterday) the first bug was fixed with the fixVersion 0.4.8 (instead of 0.4.7). Wasn't the version 0.4.7 intended for end of November/next month? When can the official 0.4.7-version be expected and will in be a plain copy of the last version available on iso.reactos.org which states "0.4.7" in it's file name?
With the move to Git, the revision number format changed from like this r76032 to like this 0.4.7-dev-701-gb46d3ce5e9, so when they branched for a 0.4.7 release, the version number went up and changed to be like this 0.4.8-dev-19-g840320cbd1. When the 0.4.8 master is branched for the 0.4.8 release, you will see that the number will have moved up again.

Before a release is out, you may see in JIRA, bug fixes with fixed version of 0.4.7 as well as 0.4.8. If the developers think that it should go into the 0.4.7 release, you will see 0.4.7 as the fixed version, else it will have a fixed version of 0.4.8.

When they branch for a release, the branch is worked on to fix as many bugs as possible, to make it a reasonably stable a release. There will still be some bugs in the release, but it will be a more stable version than the actual version it was branched from.
Thanks for the explanation. I was kind of confused.

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests