FINAL v1.0 RELEASE BURN DOWN

[vbatts]

• runc merged support Update runtime spec to rc5 runc#1370 ( @crosbymichael & @mrunalp )
• PR for docker rebase on this newer runc (for testing coverage) Update to runc master(rc5) for v0.2.x branch containerd/containerd#778 ( @crosbymichael )
• PR for cri-o rebase on this newer runc ( @mrunalp )
• final sanity check (build consistency, terminology consistency) ( err'body )

Time frame: by the March 29nd, 2017 to open the vote for v1.0.0 (which still has a one week voting period)

[caniszczyk]

I'd add box around notifying all OCI members to review the release before it's blessed, we can send out a note to all the OCI member technical contacts

[wking]

On Wed, Mar 15, 2017 at 04:45:19PM -0700, Chris Aniszczyk wrote: I'd add box around notifying all OCI members to review the release before it's blessed, we can send out a note to all the OCI member technical contacts

I'm not entirely clear on where the discussion ended up, but at least @RobDolinMS was arguing for voting on an rc6 next week and making that the hopefuly-final RC before 1.0 [1] with a 30-day review window before 1.0. That gives Members time to look things over ahead of time so they can suggest changes. If we cut 1.0 without a suitable review period, the only option open to Members who discover something they aren't comfortable with is resignation from the OCI [2]. And personally, I'll be pleasantly surprised if the 16 unmilestoned issues and PRs [3] get settled by next week. [1]: http://ircbot.wl.linuxfoundation.org/meetings/opencontainers/2017/opencontainers.2017-03-15-21.02.log.html#l-153 [2]: https://www.opencontainers.org/about/governance §8.d [3]: https://github.com/opencontainers/runtime-spec/issues?utf8=%E2%9C%93&q=is%3Aopen%20no%3Amilestone

[caniszczyk]

@vbatts re the image-spec, will there be a similar issue like this?

[vbatts]

@caniszczyk good call. I'll write it up, though the reliance on implementations being on the latest isn't just like runc.

[vbatts]

@crosbymichael is there pr to link for the docker rebase?

@mrunalp is there pr to link for cri-o rebase?

[wking]

From today's meeting, cri-o is waiting on opencontainers/runtime-tools#349.

[caniszczyk]

@crosbymichael is there a docker issue open for the rebase?

[vbatts]

i asked today. He said there is a contributor working on it, but no PR yet.

…

On Mon, Apr 3, 2017 at 7:17 PM Chris Aniszczyk ***@***.***> wrote: @crosbymichael <https://github.com/crosbymichael> is there a docker issue open for the rebase? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#726 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEF6arOk7PWcShkmRhahAxWD7TbJtDnks5rsX4bgaJpZM4MelCm> .

[philips]

@vbatts what is the new ETA as March 29th has passed.

[vbatts]

@philips great question. The big thing was seeing green tests on docker and cri-o being rebased, which is not a hard requirement, but just a nice-to-have.

[mrunalp]

We updated cri-o to latest runtime-spec/runc. cri-o/cri-o#447