[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#766054: RC bugs in GNUstep packages



At Tue, 28 Oct 2014 20:04:47 +0100,
Paul Gevers wrote:
> [Can we have this discussion in one of your d-mentors discussions, so
> that it is in the open? I don't like private discussions.]

Certainly, let's move it to the gnustep-make RFS bug although I'm not
sure if that's appropriate.

> On 28-10-14 07:48, Yavor Doganov wrote:
> > I also think it is tad too late, but that's probably better as the
> > release team will have control over the migration.
> 
> Yes, but you need to take action. The release team will not "find
> out by themselves".

Of course; I was planning to do it once I figure out the possibilites.
Obviously, some packages have to be sacrificed and won't make it to
jessie.  I need to evaluate the whole situation and present correct
information/options to the release team in order to enable them to
make a decision.

> Also, the fact that you added non RC related updates in the packages
> degrades the changes with the release team.

I only did that because I assumed that the package would be uploaded
in time so that it migrates before the freeze.

> If the packages don't migrate to testing, they also block RC fixes
> in the trivial way.  Have you read the freeze policy [1]? This is
> also the reason why I won't be uploading your other packages to
> unstable until I see a response from the release team.

Yes, I'm aware of the freeze policy.
Meanwhile, I think a release team member has reduced the migration
period to 5 days so it'll make it before the freeze.

> > Marking the bug as jessie-ignore is an acceptable solution, I think,
> > because there won't be library transitions for jessie so the bug won't
> > be exposed.  However, this will prevent us fixing grr.app's #754838,
> > but that's probably a no-op as it requires new rsskit/grr.app releases
> > which won't be accepted for jessie.  OTOH, there are a few other bugs
> > (#749721, #755514, #756852/#756853) which may be affected by the new
> > gnustep-make behavior.  I'll have to think which is the lesser evil.
> 
> Please, pretty please, discuss this with the release team a.s.a.p., i.e.
> before the freeze.

I'll try to do it before the freeze.


Reply to: