On Tue, Jun 21, 2016 at 11:30 AM, Dusty Mabe 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 Release
>> was going to include a cut-over of our back end Release Infrastructure
On Tue, Jun 21, 2016 at 11:28 AM, Jason Brooks wrote:
> On Tue, Jun 21, 2016 at 9:21 AM, Adam Miller
> wrote:
>> Hello all,
>> The original schedule for today's Fedora Two-Week Atomic Release
>> was going to include a cut-over of our back
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
Ahh, that explains why Atomic was missing from:
https://getfedora.org/en/cloud/download/index.html this morning.
On 06/21, Jason Brooks wrote:
> On Tue, Jun 21, 2016 at 9:21 AM, Adam Miller
> wrote:
> > Hello all,
> > The original schedule for today's
On 06/21/2016 12:21 PM, Adam Miller wrote:
> Hello all,
Hey Adam,
> 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
On Tue, Jun 21, 2016 at 9:21 AM, Adam Miller
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
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