Hello all, The original schedule for today's Fedora Two-Week Atomic Release was going to include a cut-over of our back end Release Infrastructure and AutoCloud automated QA environment to be compose based (one of the building blocks we need in place to make the future of the release process more flexible). However, because of the most recent Fedora 24 release slip this has caused a conflict of schedules (a schedule that was agreed upon at the Cloud FAD a few weeks ago) and as a side effect of the Fedora 24 GA event we are currently in a Fedora Infrastructure Freeze. During this Freeze, we can not make the back end changes needed to cut over to the new versions of the RelEng Composer and AutoCloud which are currently hosting the Fedora 24 Atomic Images.
This is something that slipped through the cracks and ultimately lands on me, and for that I would like to apologize to members of Project Atomic, Fedora Cloud WG, and both project communities at large.
That being said, we have a couple of options on how to handle this and I would like to request feedback from others.
We can slip the Fedora 24 Based Two-Week Atomic Release by 1 week just as the Fedora 24 GA Release was slipped and target next Tuesday (2016-06-21). This would "reset the clock" on the Two Week Releases and we will then have a Two-Week Release every two weeks following that one.
Or
We can skip this Two-Week Atomic Release all together and target the next Two-Week Atomic Release scheduled date of Tuesday 2016-07-05.
Or
We can release a Fedora 23 Based Two-Week Atomic image today (or tomorrow, pending how fast feedback rolls in) and target the next Two-Week Release window as the time to cut over to Fedora 24.
I'm open to alternate suggestions but do note that aspects of the Two Week release process are limiting at present, which is something this new Infrastructure deployment will be the starting point to resolve, so there may be restrictions on how creative of a solution we can come up with in the near term.
Once again, I would like to apologize to all who have been impacted by this and we hope that with the planned changes to the Infrastructure and the Release code will allow for more flexibility in the future.
Thank you, -AdamM
On Tue, Jun 21, 2016 at 9:21 AM, Adam Miller maxamillion@fedoraproject.org wrote:
Hello all, The original schedule for today's Fedora Two-Week Atomic Release was going to include a cut-over of our back end Release Infrastructure and AutoCloud automated QA environment to be compose based (one of the building blocks we need in place to make the future of the release process more flexible). However, because of the most recent Fedora 24 release slip this has caused a conflict of schedules (a schedule that was agreed upon at the Cloud FAD a few weeks ago) and as a side effect of the Fedora 24 GA event we are currently in a Fedora Infrastructure Freeze. During this Freeze, we can not make the back end changes needed to cut over to the new versions of the RelEng Composer and AutoCloud which are currently hosting the Fedora 24 Atomic Images.
This is something that slipped through the cracks and ultimately lands on me, and for that I would like to apologize to members of Project Atomic, Fedora Cloud WG, and both project communities at large.
That being said, we have a couple of options on how to handle this and I would like to request feedback from others.
We can slip the Fedora 24 Based Two-Week Atomic Release by 1 week just as the Fedora 24 GA Release was slipped and target next Tuesday (2016-06-21). This would "reset the clock" on the Two Week Releases and we will then have a Two-Week Release every two weeks following that one.
I vote for this option, slip a week, reset the clock.
Jason
Or
We can skip this Two-Week Atomic Release all together and target the next Two-Week Atomic Release scheduled date of Tuesday 2016-07-05.
Or
We can release a Fedora 23 Based Two-Week Atomic image today (or tomorrow, pending how fast feedback rolls in) and target the next Two-Week Release window as the time to cut over to Fedora 24.
I'm open to alternate suggestions but do note that aspects of the Two Week release process are limiting at present, which is something this new Infrastructure deployment will be the starting point to resolve, so there may be restrictions on how creative of a solution we can come up with in the near term.
Once again, I would like to apologize to all who have been impacted by this and we hope that with the planned changes to the Infrastructure and the Release code will allow for more flexibility in the future.
Thank you, -AdamM
On Tue, Jun 21, 2016 at 11:28 AM, Jason Brooks jbrooks@redhat.com wrote:
On Tue, Jun 21, 2016 at 9:21 AM, Adam Miller maxamillion@fedoraproject.org wrote:
Hello all, The original schedule for today's Fedora Two-Week Atomic Release was going to include a cut-over of our back end Release Infrastructure and AutoCloud automated QA environment to be compose based (one of the building blocks we need in place to make the future of the release process more flexible). However, because of the most recent Fedora 24 release slip this has caused a conflict of schedules (a schedule that was agreed upon at the Cloud FAD a few weeks ago) and as a side effect of the Fedora 24 GA event we are currently in a Fedora Infrastructure Freeze. During this Freeze, we can not make the back end changes needed to cut over to the new versions of the RelEng Composer and AutoCloud which are currently hosting the Fedora 24 Atomic Images.
This is something that slipped through the cracks and ultimately lands on me, and for that I would like to apologize to members of Project Atomic, Fedora Cloud WG, and both project communities at large.
That being said, we have a couple of options on how to handle this and I would like to request feedback from others.
We can slip the Fedora 24 Based Two-Week Atomic Release by 1 week just as the Fedora 24 GA Release was slipped and target next Tuesday (2016-06-21). This would "reset the clock" on the Two Week Releases and we will then have a Two-Week Release every two weeks following that one.
I vote for this option, slip a week, reset the clock.
+1 - This one is my preference as well.
-AdamM
Jason
Or
We can skip this Two-Week Atomic Release all together and target the next Two-Week Atomic Release scheduled date of Tuesday 2016-07-05.
Or
We can release a Fedora 23 Based Two-Week Atomic image today (or tomorrow, pending how fast feedback rolls in) and target the next Two-Week Release window as the time to cut over to Fedora 24.
I'm open to alternate suggestions but do note that aspects of the Two Week release process are limiting at present, which is something this new Infrastructure deployment will be the starting point to resolve, so there may be restrictions on how creative of a solution we can come up with in the near term.
Once again, I would like to apologize to all who have been impacted by this and we hope that with the planned changes to the Infrastructure and the Release code will allow for more flexibility in the future.
Thank you, -AdamM
On 06/21/2016 12:21 PM, Adam Miller wrote:
Hello all,
Hey Adam,
The original schedule for today's Fedora Two-Week Atomic Releasewas going to include a cut-over of our back end Release Infrastructure and AutoCloud automated QA environment to be compose based (one of the building blocks we need in place to make the future of the release process more flexible). However, because of the most recent Fedora 24 release slip this has caused a conflict of schedules (a schedule that was agreed upon at the Cloud FAD a few weeks ago) and as a side effect of the Fedora 24 GA event we are currently in a Fedora Infrastructure Freeze. During this Freeze, we can not make the back end changes needed to cut over to the new versions of the RelEng Composer and AutoCloud which are currently hosting the Fedora 24 Atomic Images.
Thanks for the update.
This is something that slipped through the cracks and ultimately lands on me, and for that I would like to apologize to members of Project Atomic, Fedora Cloud WG, and both project communities at large.
That being said, we have a couple of options on how to handle this and I would like to request feedback from others.
We can slip the Fedora 24 Based Two-Week Atomic Release by 1 week just as the Fedora 24 GA Release was slipped and target next Tuesday (2016-06-21). This would "reset the clock" on the Two Week Releases and we will then have a Two-Week Release every two weeks following that one.
I would vote for this one.
If we go this path could we link here to a candidate 2WA image that we would release next Tuesday? We could then focus some manual testing on this image and make sure we are A OK for next weeks release.
Or
We can skip this Two-Week Atomic Release all together and target the next Two-Week Atomic Release scheduled date of Tuesday 2016-07-05.
Or
We can release a Fedora 23 Based Two-Week Atomic image today (or tomorrow, pending how fast feedback rolls in) and target the next Two-Week Release window as the time to cut over to Fedora 24.
I'm open to alternate suggestions but do note that aspects of the Two Week release process are limiting at present, which is something this new Infrastructure deployment will be the starting point to resolve, so there may be restrictions on how creative of a solution we can come up with in the near term.
Once again, I would like to apologize to all who have been impacted by this and we hope that with the planned changes to the Infrastructure and the Release code will allow for more flexibility in the future.
Thank you, -AdamM
On Tue, Jun 21, 2016 at 11:30 AM, Dusty Mabe dusty@dustymabe.com wrote:
On 06/21/2016 12:21 PM, Adam Miller wrote:
Hello all,
Hey Adam,
The original schedule for today's Fedora Two-Week Atomic Releasewas going to include a cut-over of our back end Release Infrastructure and AutoCloud automated QA environment to be compose based (one of the building blocks we need in place to make the future of the release process more flexible). However, because of the most recent Fedora 24 release slip this has caused a conflict of schedules (a schedule that was agreed upon at the Cloud FAD a few weeks ago) and as a side effect of the Fedora 24 GA event we are currently in a Fedora Infrastructure Freeze. During this Freeze, we can not make the back end changes needed to cut over to the new versions of the RelEng Composer and AutoCloud which are currently hosting the Fedora 24 Atomic Images.
Thanks for the update.
This is something that slipped through the cracks and ultimately lands on me, and for that I would like to apologize to members of Project Atomic, Fedora Cloud WG, and both project communities at large.
That being said, we have a couple of options on how to handle this and I would like to request feedback from others.
We can slip the Fedora 24 Based Two-Week Atomic Release by 1 week just as the Fedora 24 GA Release was slipped and target next Tuesday (2016-06-21). This would "reset the clock" on the Two Week Releases and we will then have a Two-Week Release every two weeks following that one.
I would vote for this one.
+1
If we go this path could we link here to a candidate 2WA image that we would release next Tuesday? We could then focus some manual testing on this image and make sure we are A OK for next weeks release.
Images are here: https://kojipkgs.fedoraproject.org/compose/twoweek/
We shouldn't need any manual testing, these images are already being tested by the new Autocloud just as the current ones are but the new system isn't in Production yet and therefore isn't feeding fedmsg data into Datagrepper which is what the 2WA release script queries and uses the resulting metadata to populate fields for the rest of the release process including the information it then passes over fedmsg to update the websites.
-AdamM
Or
We can skip this Two-Week Atomic Release all together and target the next Two-Week Atomic Release scheduled date of Tuesday 2016-07-05.
Or
We can release a Fedora 23 Based Two-Week Atomic image today (or tomorrow, pending how fast feedback rolls in) and target the next Two-Week Release window as the time to cut over to Fedora 24.
I'm open to alternate suggestions but do note that aspects of the Two Week release process are limiting at present, which is something this new Infrastructure deployment will be the starting point to resolve, so there may be restrictions on how creative of a solution we can come up with in the near term.
Once again, I would like to apologize to all who have been impacted by this and we hope that with the planned changes to the Infrastructure and the Release code will allow for more flexibility in the future.
Thank you, -AdamM
cloud mailing list cloud@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
On 06/21/2016 09:21 AM, Adam Miller wrote:
We can slip the Fedora 24 Based Two-Week Atomic Release by 1 week just as the Fedora 24 GA Release was slipped and target next Tuesday (2016-06-21). This would "reset the clock" on the Two Week Releases and we will then have a Two-Week Release every two weeks following that one.
I'm for getting it out as soon as we can.
Incidentally, is there an ISO I can pull anywhere? For my testing?
On Tue, Jun 21, 2016 at 1:04 PM, Josh Berkus jberkus@redhat.com wrote:
On 06/21/2016 09:21 AM, Adam Miller wrote:
We can slip the Fedora 24 Based Two-Week Atomic Release by 1 week just as the Fedora 24 GA Release was slipped and target next Tuesday (2016-06-21). This would "reset the clock" on the Two Week Releases and we will then have a Two-Week Release every two weeks following that one.
I'm for getting it out as soon as we can.
Incidentally, is there an ISO I can pull anywhere? For my testing?
Yes, sorry. I meant to include this in the original email.
The new item is part of the new compose process which will reside here:
https://kojipkgs.fedoraproject.org/compose/twoweek/
-AdamM
--
Josh Berkus Project Atomic Red Hat OSAS _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
Incidentally, is there an ISO I can pull anywhere? For my testing?
Yes, sorry. I meant to include this in the original email.
The new item is part of the new compose process which will reside here:
Hmm. I was hoping to be able to install Fedora24 Atomic for my Summit Demo. That directory tree doesn't include any ISOs AFAICT.
Does anyone know where I can get ISO images in the next 24 hours?
On 06/22/2016 06:46 PM, Josh Berkus wrote:
Incidentally, is there an ISO I can pull anywhere? For my testing?
Yes, sorry. I meant to include this in the original email.
The new item is part of the new compose process which will reside here:
Hmm. I was hoping to be able to install Fedora24 Atomic for my Summit Demo. That directory tree doesn't include any ISOs AFAICT.
Does anyone know where I can get ISO images in the next 24 hours?
You mean like here?
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-24-20160622...
On 06/22/2016 08:23 PM, Dusty Mabe wrote:
On 06/22/2016 06:46 PM, Josh Berkus wrote:
Incidentally, is there an ISO I can pull anywhere? For my testing?
Yes, sorry. I meant to include this in the original email.
The new item is part of the new compose process which will reside here:
Hmm. I was hoping to be able to install Fedora24 Atomic for my Summit Demo. That directory tree doesn't include any ISOs AFAICT.
Does anyone know where I can get ISO images in the next 24 hours?
You mean like here?
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-24-20160622...
That directory wasn't there yesterday ...
On Tue, Jun 21, 2016 at 11:21:42AM -0500, Adam Miller wrote:
We can slip the Fedora 24 Based Two-Week Atomic Release by 1 week just
Or
We can skip this Two-Week Atomic Release all together and target the next Two-Week Atomic Release scheduled date of Tuesday 2016-07-05.
Or
We can release a Fedora 23 Based Two-Week Atomic image today (or tomorrow, pending how fast feedback rolls in) and target the next
I think any of these is fine. I have a slight preference for the first option from just a high-level perspective, but ultimately, whatever the teams working on it actually prefer.
-
Adam Miller -
Dusty Mabe -
Jason Brooks -
Josh Berkus -
Matthew Miller