New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plan rc0 tag #4

Closed
cryptapus opened this Issue Jan 2, 2019 · 4 comments

Comments

Projects
None yet
2 participants
@cryptapus
Copy link

cryptapus commented Jan 2, 2019

Unless there are any objections, I'll plan to attempt a beta0 test build via gitian on wk1903.

@cryptapus cryptapus added this to the Release 0.16.3.0-beta0 milestone Jan 2, 2019

@cryptapus cryptapus self-assigned this Jan 2, 2019

@cryptapus cryptapus added the release label Jan 2, 2019

@Pttn

This comment has been minimized.

Copy link

Pttn commented Jan 4, 2019

I support this. We should also set some deadlines for Release Candidate and final version as no major problem were reported since clo1 released the code months ago.
We could make a RC build on early February (Week 1906) and the final release 1 month later (Week 1910)?

@cryptapus

This comment has been minimized.

Copy link
Author

cryptapus commented Jan 10, 2019

If #6 is merged, I don't see any reason why we couldn't move to a release fairly quickly since it allows flexible upgrades via BIP9. If a beta0 release proves gitian is working well I will propose an immediate move to RC0 and a couple of weeks to confirm mining BIP9 blocks isn't forking anything.

@Pttn

This comment has been minimized.

Copy link

Pttn commented Jan 10, 2019

Fine, let's do this. In this case we don't even need a bêta release, we can ensure first that Gitian build works then directly label the build RC, and finally wait some time before final release.

@cryptapus cryptapus changed the title Plan beta0 tag and gitian build Plan rc0 tag Jan 10, 2019

@cryptapus

This comment has been minimized.

Copy link
Author

cryptapus commented Jan 13, 2019

@cryptapus cryptapus closed this Jan 13, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment