Re: managing transitions (was: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental)

2015-10-06 Thread Barry Warsaw
On Oct 06, 2015, at 08:39 AM, Brian May wrote:

>On Tue, 6 Oct 2015 at 18:46 Thomas Goirand  wrote:
>
>> This IMO is the same topic as having a Gerrit review system (and not
>> just Git) which could do tests on each change of a package even before
>> having them committed to our git.
>>
>
>Sounds like an interesting thing to discuss/test after we move to git...

I don't intend to bikeshed this, nor do I have time to do the work, so in our
do-it-ocracy any online review system would be a fantastic addition.  I'll
just point to GitLab community edition as a nice open source option in this
space.

Cheers,
-Barry



Re: managing transitions (was: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental)

2015-10-06 Thread Thomas Goirand
On 10/05/2015 11:11 PM, Barry Warsaw wrote:
> On Oct 05, 2015, at 02:51 PM, Thomas Goirand wrote:
> 
>> In other distributions (Red Hat and Ubuntu), everyone is aware of this
>> kind of issue before uploading, and this kinds of things don't happen.
> 
> Ubuntu at least does have a technical solution that helps ameliorate
> archive-wide breakages, and that is -proposed migration.  When you upload
> e.g. to wily, it gets diverted to wily-proposed and to get promoted it has to
> pass a number of tests.  The package and their reverses have to build.  DEP-8
> tests have to pass, etc.  You can get a nice report about which -proposed
> promotions are failing:
> 
> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html

Oh, nice! We do need something like this too.

> The downside is that you should probably be proactively checking this list
> (poll vs ping) and it can sometimes be difficult to figure out why a promotion
> fails or how to fix it.

It's a super nice tool, though in some cases, I do see that we may want
to ignore it. For example, dozens of packages passing, and just a single
leaf one with some issues.

> But this does mean that the archive itself is very rarely broken, and it can
> be a convenient way to stage package updates that may have effects in parts of
> the archive you might not be aware of.

If we need the compute power to do it, I have a few proposal for that.
I'm all for having a CI / CD also for packages.

This IMO is the same topic as having a Gerrit review system (and not
just Git) which could do tests on each change of a package even before
having them committed to our git.

Thomas



Re: managing transitions (was: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental)

2015-10-06 Thread Brian May
On Tue, 6 Oct 2015 at 18:46 Thomas Goirand  wrote:

> This IMO is the same topic as having a Gerrit review system (and not
> just Git) which could do tests on each change of a package even before
> having them committed to our git.
>

Sounds like an interesting thing to discuss/test after we move to git...


Re: managing transitions (was: python-networkx_1.10-1_amd64.changes ACCEPTED into experimental)

2015-10-06 Thread Mattia Rizzolo
On Tue, Oct 06, 2015 at 08:39:48AM +, Brian May wrote:
> On Tue, 6 Oct 2015 at 18:46 Thomas Goirand  wrote:
> 
> > This IMO is the same topic as having a Gerrit review system (and not
> > just Git) which could do tests on each change of a package even before
> > having them committed to our git.
> >
> 
> Sounds like an interesting thing to discuss/test after we move to git...

Moreover, jenkins.debian.org is happening right about now, guess it
would help quite something (and I'd be happy to host such tests there).

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature