0.6 release readiness

[Kamil Paral]

Hello,

we have finished working on some important tickets. I want to discuss the readiness to release AutoQA 0.6.0.

See the current tickets:
https://fedorahosted.org/autoqa/milestone/0.6.0

Please note that ticket #330, albeit not yet closed, is also finished. I just want to amend the documentation only closely before the release.

Important finished tickets that I'd like to see in production soon:
 *  Depcheck - prefilter the list of packages passed to yum instance's rpmdb
    https://fedorahosted.org/autoqa/ticket/349
 *  upgradepath: improve behavior when pushing update to multiple releases
    https://fedorahosted.org/autoqa/ticket/330

Almost finished tickets:
 *  Custom 404 page for autoqa.fp.o
    https://fedorahosted.org/autoqa/ticket/354

The rest of the tickets will probably take some more time and are not ready yet.

I think that #354 is easy enough to be finished in a day. I propose waiting for that one and then releasing 0.6.0. That means that 0.6.0 would be released some day this week. The rest of the tickets would move to 0.7 (or more precisely - we'll discuss that at 0.7 planning stage).

Comments?

[Tim Flink]

On Mon, 1 Aug 2011 07:24:10 -0400 (EDT)
Kamil Paral  wrote:
> Hello,
>
> we have finished working on some important tickets. I want to discuss
> the readiness to release AutoQA 0.6.0.
> The rest of the tickets will probably take some more time and are not
> ready yet.

Is it worth waiting for #347 (urls in bodhi)? I think that the autoqa
parts are easy - I could get that code done today.

However, I'm not as sure about the infrastructure changes that would be
needed. Martin made a .spec for yourls (haven't looked at it yet) and I
would still need to make one for the client. After all that is done, we
would need to set YOURLS up in production and that might be pushing it
for release this week (especially if we want the packages in
fedora+EPEL)

Thoughts?

Tim

[James Laska]

On Mon, 2011-08-01 at 08:31 -0600, Tim Flink wrote:
> On Mon, 1 Aug 2011 07:24:10 -0400 (EDT)
> Kamil Paral  wrote:
> > Hello,
> >
> > we have finished working on some important tickets. I want to discuss
> > the readiness to release AutoQA 0.6.0.
> > The rest of the tickets will probably take some more time and are not
> > ready yet.
>
> Is it worth waiting for #347 (urls in bodhi)? I think that the autoqa
> parts are easy - I could get that code done today.
>
> However, I'm not as sure about the infrastructure changes that would be
> needed. Martin made a .spec for yourls (haven't looked at it yet) and I
> would still need to make one for the client. After all that is done, we
> would need to set YOURLS up in production and that might be pushing it
> for release this week (especially if we want the packages in
> fedora+EPEL)
>
> Thoughts?

My $0.02 ... if that's not ready in the next day or so ... let's just
release with what we have and line that up for the next release.  My
impression is that it would take a more than this week to get packaging,
deployment+configuration, autoqa integration and testing completed.

Of course, my involvement in this release is fairly low-key (package
building + push) ... so whatever the group feels is appropriate.

Thanks,
James

[Kamil Paral]

> Hello,
>
> we have finished working on some important tickets. I want to discuss
> the readiness to release AutoQA 0.6.0.
>
> See the current tickets:
> https://fedorahosted.org/autoqa/milestone/0.6.0
>
> Please note that ticket #330, albeit not yet closed, is also finished.
> I just want to amend the documentation only closely before the
> release.
>
> Important finished tickets that I'd like to see in production soon:
> Depcheck - prefilter the list of packages passed to yum instance's
>
> rpmdb
> https://fedorahosted.org/autoqa/ticket/349
> upgradepath: improve behavior when pushing update to multiple
>
> releases
> https://fedorahosted.org/autoqa/ticket/330
>
> Almost finished tickets:
> Custom 404 page for autoqa.fp.o
>
> https://fedorahosted.org/autoqa/ticket/354

The last ticket has landed. So what's the plan now? Are we OK we just performing a few tests on our local machines and then releasing it, or do we want to have it running for a few days on some testing server (similarly to the previous release)? Don't forget our mascot when deciding! [1]

I must admit I'll impatient a little, I'd test today and release tomorrow.

[1] http://troll.me/images/the-most-interesting-man-in-the-world/i-dont-always-t...

[Tim Flink]

On Wed, 3 Aug 2011 09:54:21 -0400 (EDT)
Kamil Paral  wrote:
> The last ticket has landed. So what's the plan now? Are we OK we just
> performing a few tests on our local machines and then releasing it,
> or do we want to have it running for a few days on some testing
> server (similarly to the previous release)? Don't forget our mascot
> when deciding! [1]

I don't see anything huge right now that would prevent us from releasing
this week. I'll get testing today.
> I must admit I'll impatient a little, I'd test today and release
> tomorrow.

Probably best not to release on Friday in case there are problems -
either tomorrow or Monday, I think.

Tim

[Tim Flink]

On Wed, 3 Aug 2011 08:38:05 -0600
Tim Flink  wrote:
> On Wed, 3 Aug 2011 09:54:21 -0400 (EDT)
> Kamil Paral  wrote:
> > The last ticket has landed. So what's the plan now? Are we OK we
> > just performing a few tests on our local machines and then
> > releasing it, or do we want to have it running for a few days on
> > some testing server (similarly to the previous release)? Don't
> > forget our mascot when deciding! [1]
>
> I don't see anything huge right now that would prevent us from
> releasing this week. I'll get testing today.

As an update - I haven't been able to test 0.6.0 today. Long story
short - my internet connection went out and I've been trying to rebuild
a test system while sitting in a coffee shop.

Tim

[Kamil Paral]

> As an update - I haven't been able to test 0.6.0 today. Long story
> short - my internet connection went out and I've been trying to
> rebuild
> a test system while sitting in a coffee shop.

I performed an hour of testing, everything seems fine. I pushed one little improvement in upgradepath and found some stray pending builds. I did not encounter any bug in upgradepath nor depcheck. I think we are ready to go.

[Josef Skladanka]

+1 on the "ready to go" thought ;-)

----- Original Message -----
> From: "Kamil Paral" 
> To: "AutoQA development" 
> Sent: Thursday, August 4, 2011 12:03:25 PM
> Subject: Re: 0.6 release readiness
> > As an update - I haven't been able to test 0.6.0 today. Long story
> > short - my internet connection went out and I've been trying to
> > rebuild
> > a test system while sitting in a coffee shop.
>
> I performed an hour of testing, everything seems fine. I pushed one
> little improvement in upgradepath and found some stray pending builds.
> I did not encounter any bug in upgradepath nor depcheck. I think we
> are ready to go.
> _______________________________________________
> autoqa-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/autoqa-devel