Skip to content
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

FINAL v1.0 RELEASE BURN DOWN #615

Closed
2 tasks done
vbatts opened this issue Mar 16, 2017 · 12 comments
Closed
2 tasks done

FINAL v1.0 RELEASE BURN DOWN #615

vbatts opened this issue Mar 16, 2017 · 12 comments
Milestone

Comments

@vbatts
Copy link
Member

vbatts commented Mar 16, 2017

  • implementations on latest RC (need some citations here)
  • final sanity check (build consistency, terminology consistency) ( err'body )
@vbatts
Copy link
Member Author

vbatts commented Mar 16, 2017

cc @caniszczyk

@caniszczyk caniszczyk changed the title FINAL RELEASE BURN DOWN FINAL v1.0 RELEASE BURN DOWN Mar 20, 2017
@caniszczyk
Copy link
Contributor

@vbatts sounds good, how do other @opencontainers/image-spec-maintainers feel?

@RobDolinMS
Copy link
Collaborator

AFAIK, the image spec needs hyperlinks to sections. @vbatts - Would you please add that to the release burndown checklist?

@erikh
Copy link
Contributor

erikh commented Mar 21, 2017 via email

@erikh
Copy link
Contributor

erikh commented Mar 21, 2017

#621 created for @RobDolinMS's issue

@vbatts vbatts added this to the v1.0.0 milestone Mar 22, 2017
@philips
Copy link
Contributor

philips commented Apr 13, 2017

Are there updates on this burndown? Are these the only two remaining issues everyone agrees upon? https://github.com/opencontainers/image-spec/milestone/3

If so +1 on getting this shipped.

@wking
Copy link
Contributor

wking commented Apr 13, 2017 via email

@stevvooe
Copy link
Contributor

I would expect we do an rc6 before a 1.0. The rc6 milestone has a few issues we need to work out, as well.

@mattspencer-arm
Copy link
Contributor

Hi Guys
I know this may be a bit late in the day, but ARM would like to get involved in the discussion around the arch/variant/features attributes used to identify ARM images. I am working through a sane schema at the moment and will have something to post here later today/tomorrow morning that should allow the correct description of images containing ARM binaries.
Is my best route to add an issue to enable discussion, and what are the chances of getting our proposal discussed ahead of the v1.0 release?
Cheers
Matt

@wking
Copy link
Contributor

wking commented Apr 27, 2017

Is my best route to add an issue to enable discussion...

Maybe chime in on #650 and #652?

@caniszczyk
Copy link
Contributor

@stevvooe how are you feeling about this getting close to RC6 and v1.0 FINAL? now that runtime-spec is getting close, it would be great to have both of the specs go out close to the same time (at least it will make my life easier with PR planning) opencontainers/runtime-spec#726

@stevvooe
Copy link
Contributor

stevvooe commented May 8, 2017

@stevvooe how are you feeling about this getting close to RC6 and v1.0 FINAL? now that runtime-spec is getting close, it would be great to have both of the specs go out close to the same time (at least it will make my life easier with PR planning) opencontainers/runtime-spec#726

I think we can release an rc6, but we still need to work out some issues with the platform fields before 1.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants