There is a time window for that? A bug could be there but just not found by users, so for how long developers wait before they consider RC4 as a stable version?
If no new bugs are found within a week of an RC's release, it will become the final version. 
Topic: Bitcoin Core & Milestones (Read 243 times)
The new issues and PRs are related to critical-sh bugs found in RC1 and RC2. The final version will be released when those bugs are resolved and no new ones are found with the next RC.
There is a time window for that? A bug could be there but just not found by users, so for how long developers wait before they consider RC4 as a stable version?
The new issues and PRs are related to critical-sh bugs found in RC1 and RC2. The final version will be released when those bugs are resolved and no new ones are found with the next RC.
I was watching the milestones[1] page in GitHub, Issues were being closed until we reached 96% a few hours ago with only:
and now more has been added. Are those necessarily coming from either 0.16.0 RC1 or RC2? and as long as people keep reporting bugs, the final version won't be released? I never understood how the release schedule works.
[1] https://github.com/bitcoin/bitcoin/milestone/30
Code:
Release schedule for 0.16.0
TODO for release notes 0.16.0 Docs
TODO for release notes 0.16.0 Docs
and now more has been added. Are those necessarily coming from either 0.16.0 RC1 or RC2? and as long as people keep reporting bugs, the final version won't be released? I never understood how the release schedule works.
[1] https://github.com/bitcoin/bitcoin/milestone/30
Jump to: