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

Release schedule for 0.16.0 #11449

Closed
laanwj opened this Issue Oct 4, 2017 · 13 comments

Comments

Projects
None yet
6 participants
@laanwj
Member

laanwj commented Oct 4, 2017

Here is a proposed release schedule for 0.16.0. Like for previous major releases I've added 6 months to the previous release schedule (#9961), as well as two extra for segwit wallet release 0.15.1.

(removed proposed schedule, see below)

@instagibbs

This comment has been minimized.

Show comment
Hide comment
@instagibbs

instagibbs Oct 5, 2017

Member

- Finalize and close translations for 0.14

Member

instagibbs commented Oct 5, 2017

- Finalize and close translations for 0.14

@laanwj

This comment has been minimized.

Show comment
Hide comment
@laanwj

laanwj Oct 5, 2017

Member
  • Finalize and close translations for 0.14

That's correct. Translations are maintained for the last two major releases, the ones before that are closed on transifex (and after that, merged into the appropriate branch one last time). So when 0.16 is released, this will be 0.14.

Member

laanwj commented Oct 5, 2017

  • Finalize and close translations for 0.14

That's correct. Translations are maintained for the last two major releases, the ones before that are closed on transifex (and after that, merged into the appropriate branch one last time). So when 0.16 is released, this will be 0.14.

@laanwj

This comment has been minimized.

Show comment
Hide comment
@laanwj

laanwj Jan 11, 2018

Member

Because 0.16 is a special "theme" release (let's not do this again) for segwit wallet, we're going to try to do this release sooner if possible (when all blockers in https://github.com/bitcoin/bitcoin/milestone/30 have been addressed). The timeline here is the worst-case projection.

Member

laanwj commented Jan 11, 2018

Because 0.16 is a special "theme" release (let's not do this again) for segwit wallet, we're going to try to do this release sooner if possible (when all blockers in https://github.com/bitcoin/bitcoin/milestone/30 have been addressed). The timeline here is the worst-case projection.

@cncr04s

This comment has been minimized.

Show comment
Hide comment
@cncr04s

cncr04s Jan 19, 2018

It's been a while since the last major release. The community would benefit from reassurance that issues are being addressed, and will be released soon.

cncr04s commented Jan 19, 2018

It's been a while since the last major release. The community would benefit from reassurance that issues are being addressed, and will be released soon.

@MeshCollider

This comment has been minimized.

Show comment
Hide comment
@MeshCollider

MeshCollider Jan 19, 2018

Member

@cncr04s as you can see from the schedule, it has only really been a couple months, major releases are done every 6 months or so normally, so we're far ahead of schedule not behind

Member

MeshCollider commented Jan 19, 2018

@cncr04s as you can see from the schedule, it has only really been a couple months, major releases are done every 6 months or so normally, so we're far ahead of schedule not behind

@laanwj

This comment has been minimized.

Show comment
Hide comment
@laanwj

laanwj Jan 19, 2018

Member

The community would benefit from reassurance that issues are being addressed, and will be released soon.

A lot of development is continuously happening, see https://github.com/bitcoin/bitcoin/commits/master

IF you want to speed up the release, then help testing or review for the existing PRs (see the milestone link above). Posting impatient messages here will do nothing.

Member

laanwj commented Jan 19, 2018

The community would benefit from reassurance that issues are being addressed, and will be released soon.

A lot of development is continuously happening, see https://github.com/bitcoin/bitcoin/commits/master

IF you want to speed up the release, then help testing or review for the existing PRs (see the milestone link above). Posting impatient messages here will do nothing.

@laanwj

This comment has been minimized.

Show comment
Hide comment
@laanwj

laanwj Jan 30, 2018

Member

The 0.16 branch was split off, and 0.16.0rc1 has just been tagged.

Member

laanwj commented Jan 30, 2018

The 0.16 branch was split off, and 0.16.0rc1 has just been tagged.

@RossClelland

This comment has been minimized.

Show comment
Hide comment
@RossClelland

RossClelland Jan 31, 2018

Hello, daft question but you're original post mentioned the branch and rc1 tag happening in April but the post above suggests it's already complete. Does this mean the timeline has moved forward or have I missed something?
Thanks.

RossClelland commented Jan 31, 2018

Hello, daft question but you're original post mentioned the branch and rc1 tag happening in April but the post above suggests it's already complete. Does this mean the timeline has moved forward or have I missed something?
Thanks.

@instagibbs

This comment has been minimized.

Show comment
Hide comment
@instagibbs

instagibbs Jan 31, 2018

Member

@RossClelland the normal time-based release is being side-stepped for feature release(Segwit full support).

Member

instagibbs commented Jan 31, 2018

@RossClelland the normal time-based release is being side-stepped for feature release(Segwit full support).

@laanwj

This comment has been minimized.

Show comment
Hide comment
@laanwj

laanwj Feb 1, 2018

Member

Right, what @instagibbs says. To clarify I've removed the schedule.

Member

laanwj commented Feb 1, 2018

Right, what @instagibbs says. To clarify I've removed the schedule.

@RossClelland

This comment has been minimized.

Show comment
Hide comment
@RossClelland

RossClelland commented Feb 1, 2018

Thanks both

@mmortal03

This comment has been minimized.

Show comment
Hide comment
@mmortal03

mmortal03 Feb 26, 2018

@laanwj someone should close this, right?

mmortal03 commented Feb 26, 2018

@laanwj someone should close this, right?

@laanwj

This comment has been minimized.

Show comment
Hide comment
@laanwj

laanwj Feb 26, 2018

Member

Right, thanks, the release was tagged 2018-02-22 and binaries uploaded today. Closing.

Member

laanwj commented Feb 26, 2018

Right, thanks, the release was tagged 2018-02-22 and binaries uploaded today. Closing.

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