Rkt: Question: What is blocking the 1.26.0 release?

[trusch]

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]

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]

A few weeks ago the repo was moved to an new location and there are 50+
commits at least ready to test. I think dead is something else, there's
something every day (discussion etc.)

Fleet is officially dead, you are right. I know that it will be hard for
rkt with all the OCI stuff which needs to be implemented, but I think rkt
has a very good design compared to docker, so there is a chance.

I would love to see rkt evolving, cause it seems to be a good approach to
bring container isolation to embedded devices.

@coreos please tell me, if I need to redesign my software systems to use
docker...

Lord Daedra [e-mail] schrieb am Sa., 6. Mai 2017, 15:09:

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...

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rkt/rkt/issues/3664#issuecomment-299638960, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AC3LqQ1g8SIZExHCbqy9IL9mk6qA3Qqnks5r3HEDgaJpZM4NJ9OY
.

[lucab]

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]

@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]

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

[trusch]

Release PR is HERE

[lucab]

@trusch thanks, I recorded this here https://github.com/rkt/rkt/issues/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 https://github.com/rkt/rkt/issues/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.