Hi Cloud/Atomic WG,
I would like to request review of the WG deliverables for Fedora 25 release. The list of deliverables is available on wiki: https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/Fed... Please let me know, or edit the wiki page, in case there are missing deliverables or the current ones have wrong blocking status.
There is going to be overall review done by FESCo, probably on 2016-Sep-30 for all the blocking deliverables.
Thanks and Best Regards, Jan
Hi,
may I request any feedback on this topic, and/or adding this topic to the next Cloud WG meeting agenda ?
Thanks, Jan
On Wed, Sep 7, 2016 at 7:32 PM, Jan Kurik jkurik@redhat.com wrote:
Hi Cloud/Atomic WG,
I would like to request review of the WG deliverables for Fedora 25 release. The list of deliverables is available on wiki: https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/Fed... Please let me know, or edit the wiki page, in case there are missing deliverables or the current ones have wrong blocking status.
There is going to be overall review done by FESCo, probably on 2016-Sep-30 for all the blocking deliverables.
Thanks and Best Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
On Fri, Sep 16, 2016, at 04:14 AM, Jan Kurik wrote:
Hi,
may I request any feedback on this topic, and/or adding this topic to the next Cloud WG meeting agenda ?
It'd be nice to make Atomic Host a blocking deliverable - I think we have sufficient experience now and manpower to do that.
On Fri, Sep 16, 2016 at 2:27 PM, Colin Walters walters@verbum.org wrote:
On Fri, Sep 16, 2016, at 04:14 AM, Jan Kurik wrote:
Hi,
may I request any feedback on this topic, and/or adding this topic to the next Cloud WG meeting agenda ?
It'd be nice to make Atomic Host a blocking deliverable - I think we have sufficient experience now and manpower to do that.
How this should work ? I am asking because Atomic is delivered bi-weekly and Fedora releases are delivered two times a year. Perhaps delivering the last released Atomic build before Fedora release GA date might work. Any other/better ideas how this should be synchronized ?
Regards, Jan
cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-leave@lists.fedoraproject.org
On Fri, Sep 16, 2016, at 08:38 AM, Jan Kurik wrote:
How this should work ? I am asking because Atomic
BTW let's try to consistently use the term "Atomic Host" for this.
is delivered bi-weekly and Fedora releases are delivered two times a year. Perhaps delivering the last released Atomic build before Fedora release GA date might work. Any other/better ideas how this should be synchronized ?
The details of the synchronization are useful to look at, but what concerns me more is ensuring that the base system (mostly anaconda/systemd) works during the run-up to the next Fedora release. (Which for F24 it didn't).
See: https://bugzilla.redhat.com/show_bug.cgi?id=1376811 for one active issue.
On 16/09/16, Jan Kurik wrote:
On Fri, Sep 16, 2016 at 2:27 PM, Colin Walters walters@verbum.org wrote:
On Fri, Sep 16, 2016, at 04:14 AM, Jan Kurik wrote:
Hi,
may I request any feedback on this topic, and/or adding this topic to the next Cloud WG meeting agenda ?
It'd be nice to make Atomic Host a blocking deliverable - I think we have sufficient experience now and manpower to do that.
How this should work ? I am asking because Atomic is delivered bi-weekly and Fedora releases are delivered two times a year. Perhaps delivering the last released Atomic build before Fedora release GA date might work. Any other/better ideas how this should be synchronized ?
This is my understanding too. We sync up Atomic host with the latest released Fedora GA, and then follow on our normal 2-week release cycle. This does not make the 2 week atomic into the official 6month old release cycle story.
Kushal
On 07/09/16, Jan Kurik wrote:
Hi Cloud/Atomic WG,
I would like to request review of the WG deliverables for Fedora 25 release. The list of deliverables is available on wiki: https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/Fed... Please let me know, or edit the wiki page, in case there are missing deliverables or the current ones have wrong blocking status.
There is going to be overall review done by FESCo, probably on 2016-Sep-30 for all the blocking deliverables.
I thought I already replied to this mail but seems like I am wrong :( As I mentioned in the meeting last night, for F25 the current release blocking list looks good for Cloud. Only the base image is blocking for now.
Kushal