8000 Question: What is blocking the 1.26.0 release? · Issue #3664 · rkt/rkt · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Feb 24, 2020. It is now read-only.

Question: What is blocking the 1.26.0 release? #3664

Closed
trusch opened this issue Apr 27, 2017 · 7 comments
Closed

Question: What is blocking the 1.26.0 release? #3664

trusch opened this issue Apr 27, 2017 · 7 comments

Comments

@trusch
Copy link
Contributor
trusch commented Apr 27, 2017

What is blocking the release? Can I help? There are no open issues on the milestone, and the 1.25.0 release is quiet old (currently about 50 commits behind). The last releases where more often.

I would love to see the 1.26.0 release soon, so I can stop deploying my patched version of rkt to my arm devices.
@lorddaedra
Copy link

Sorry to say but the project looks dead.. Latest release was 20 February (with new releases every 2 weeks), today is 6 May...

Same story was with another project, fleet https://github.com/coreos/fleet

I hope I'm wrong...

@trusch
Copy link
Contributor Author
trusch commented May 6, 2017 via email

@lucab
Copy link
Member
lucab commented May 9, 2017 •
edited
Loading

Nothing specific is blocking 1.26.0 release, I think we can cut one pretty soon. I just added your other PR to the milestone tracker, after that lands we are ready to go. The main delayer so far has been personal backlog and some details to be sorted after CNCF move.

Fleet is indeed already on its deprecation path. rkt instead is now a CNCF project, but we are still figuring out some bits of future project directions (including the release cycle).

Now, for the practical side where you (anybody) can help: the release process is documented here. If anybody volunteers for, we can pick a release pilot to schedule/triage/prepare next release and drive it up to the release-PR point (merging/tagging/releasing requires signing keys and I can take care of it for now, we'll address that later).

@trusch would you be available as a pilot for 1.26.0? @JulienBalestra or any other ticket-subscribers volunteering for 1.27.0?

@trusch
Copy link
Contributor Author
trusch commented May 12, 2017

@lucab I'll prepare the 1.26.0 release today. Complete build is currently running, if that succeeds I will write the changelog and submit the PR.

@JulienBalestra
Copy link
Contributor

Thanks a lot @trusch !
@lucab I'll take care of the next one (1.27.0).

@trusch
Copy link
Contributor Author
trusch commented May 12, 2017

Release PR is HERE

@trusch trusch closed this as completed May 12, 2017
@lucab
Copy link
Member
lucab commented May 12, 2017

@trusch thanks, I recorded this here #3676. I set it for early next week as an estimate in case we encounter issues, and to loop in the marketing side of CNCF.

@JulienBalestra great, I also recorded it at #3677. I'm spacing this in 3 weeks (as the previous 2w cycle was very stringent and only due to coupling with OS releases), but we can later further adjust the schedule.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lucab @trusch @JulienBalestra @lorddaedra
0