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
release cycle
Moderator: Moderator Team
Re: release cycle
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 Official Twitter Account | Admin of ReactOS Turkish Twitter Account @reactos_tr
Re: release cycle
0.4.7-rc1 can be downloaded here:
https://sourceforge.net/projects/reacto ... tOS/0.4.7/
https://sourceforge.net/projects/reacto ... tOS/0.4.7/
Re: release cycle
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.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?
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 - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
The layman's guides - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.
Re: release cycle
Thanks for the explanation. I was kind of confused.oldman wrote: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.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?
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.
Who is online
Users browsing this forum: Ahrefs [Bot] and 13 guests