FINAL v1.0 RELEASE BURN DOWN #726
Comments
|
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 |
|
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
|
|
@vbatts re the image-spec, will there be a similar issue like this? |
|
@caniszczyk good call. I'll write it up, though the reliance on implementations being on the latest isn't just like runc. |
|
@crosbymichael is there pr to link for the docker rebase? @mrunalp is there pr to link for cri-o rebase? |
|
From today's meeting, cri-o is waiting on opencontainers/runtime-tools#349. |
|
@crosbymichael is there a docker issue open for the rebase? |
|
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>
.
|
|
@vbatts what is the new ETA as March 29th has passed. |
|
@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. |
|
We updated cri-o to latest runtime-spec/runc. cri-o/cri-o#447 |
|
@crosbymichael any news on the bullet item "PR for docker rebase on this newer runc (for testing coverage)" |
|
@crosbymichael post dockercon ping. I need to start doing a lot of PR planning and member outreach for the v1.0 so would love to know how timing looks on your end, along with the rest of the @opencontainers/runtime-spec-maintainers |
|
Thanks for the ping. I'll take care of it this week now that we are back from dockercon and back to development. |
|
Thanks @crosbymichael, I'll start the PR dance work that's required for getting v1.0 out the door, look forward to the dev call this week to update folks on the plan :D |
|
Sounds good, working on it today |
|
containerd PR is up containerd/containerd#778 |
|
Checked off the docker rebase. Lets schedule some time to do a final sanity check next week? |
|
@crosbymichael Awesome :) Sure, I'll set something up for next week (Sorry couldn't do it today as I got side-tracked). |
|
👍
…On Fri, May 5, 2017 at 8:07 PM Mrunal Patel ***@***.***> wrote:
@crosbymichael <https://github.com/crosbymichael> Awesome :) Sure, I'll
set something up for next week (Sorry couldn't do it today as I got
side-tracked).
—
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/AAEF6c3urCyLbq4YUYkQfUvKKqDDkmlgks5r27mhgaJpZM4MelCm>
.
|
|
very cool cc: @opencontainers/runtime-spec-maintainers for wider awareness |
|
|
|
@opencontainers/runtime-spec-maintainers, I'm syncing with the OCI PR team for v1.0 planning this afternoon, is there a strong feeling on calling for a vote this week or is there still more work to do? |
|
for runtime-spec, this seems fine. that would mean that it and image-spec
don't release a v1.0 at the same time.
…On Tue, May 16, 2017 at 12:43 PM, Chris Aniszczyk ***@***.***> wrote:
@opencontainers/runtime-spec-maintainers
<https://github.com/orgs/opencontainers/teams/runtime-spec-maintainers>,
I'm syncing with the OCI PR team for v1.0 planning this afternoon, is there
a strong feeling on calling for a vote this week or is there still more
work to do?
—
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/AAEF6dnTbAZ9nofacWjcgHZZwLnuyNleks5r6dIwgaJpZM4MelCm>
.
|
|
@vbatts, I'm not sure how close image-spec is to v1.0, maybe @stevvooe can comment At the moment, all OCI PR planning is around both going around the same time, if both runtime-spec and image-spec maintainers were willing to wait to coordinate, that would be fine, otherwise I can work with the OCI PR folks to plan things differently. I'm also generating a list of all the OCI contributors over the last couple of years to be thanked in the PR / blog post going out, I'll share that with the group before the end of this week for a sanity check |
|
On Wed, Mar 15, 2017 at 02:53:43PM -0700, Vincent Batts wrote:
[ ] final sanity check (build consistency, terminology consistency)
With 1.0.0 cut, we can probably check this off, close this issue, and
close the 1.0.0 milestone (via [1]).
[1]: https://github.com/opencontainers/runtime-spec/milestones
|
|
On Wed, Aug 02, 2017 at 08:51:31PM +0000, Chris Aniszczyk wrote:
Closed #726.
That leaves [1] 100% complete, but it's still listed as “open” on [2].
Can you mark it closed there?
[1]: https://github.com/opencontainers/runtime-spec/milestone/7
[2]: https://github.com/opencontainers/runtime-spec/milestones
|
|
On Wed, Aug 02, 2017 at 01:56:48PM -0700, W. Trevor King wrote:
On Wed, Aug 02, 2017 at 08:51:31PM +0000, Chris Aniszczyk wrote:
> Closed #726.
That leaves [1] 100% complete, but it's still listed as “open” on [2].
Can you mark it closed there?
[1]: https://github.com/opencontainers/runtime-spec/milestone/7
[2]: https://github.com/opencontainers/runtime-spec/milestones
The v1.0.0 milestone is still open on [2]. Can someone with write
access close it?
|
Time frame: by the March 29nd, 2017 to open the vote for v1.0.0 (which still has a one week voting period)
The text was updated successfully, but these errors were encountered: