[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    Re: Why are 4.8.80 packages already out in the wild?
From:       Sebastian =?ISO-8859-1?Q?K=FCgler?= <sebas () kde ! org>
Date:       2012-06-04 8:52:01
Message-ID: 1915992.PXi82WTbVn () miro
[Download RAW message or body]

On Monday, June 04, 2012 01:26:01 Kevin Kofler wrote:
> On Monday 04 June 2012, Albert Astals Cid wrote:
> > It's not about hurting or not (that it does, see how Martin got confused
> > and  probably lost time wondering how something like that could be
> > happening).
> 
> Oh, and what Martin actually got confused by is a failure of processes on
> the  KDE end: The Bugzilla entry for the new (pre)release should be created
> no later than the first "try" of tarballs. How else are we, the packagers,
> supposed to report bugs we find in the tarballs, if they're not of release-
> blocking importance? When you create the tarballs, the component should
> already be in place.

That means that people report bugs against different incarnations of the same 
packages, which makes bugs hard to find -- it doesn't work as we can't verify 
the exact state of the code a bug is filed against.

We've handled package level problems via email in direct contact with 
packagers who encountered the issues, and that worked fine so far. I suggest 
we stick to it.
-- 
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
[prev in list] [next in list] [prev in thread] [next in thread]