Dne 13.3.2013 14:28, Dennis Gilmore napsal(a):
-----BEGIN PGP SIGNED MESSAGE-----
On Wed, 13 Mar 2013 14:03:26 +0100
Vít Ondruch <vondruch(a)redhat.com> wrote:
> Dne 13.3.2013 10:09, Peter Robinson napsal(a):
>> On Wed, Mar 13, 2013 at 8:25 AM, Vít Ondruch <vondruch(a)redhat.com>
>>> Dne 12.3.2013 16:30, Dennis Gilmore napsal(a):
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>> Hi All,
>>>> F19 has been branched, please be sure to do a git pull --rebase
>>>> to pick up the new branch, additionally rawhide/f20 has had
>>>> inheritance cut off from previous releases, so this means that
>>>> anything you do for f19 you also have to do in the master branch
>>>> and do a build there.
>>> Why was it cut off so soon actually? The reason for disabling
>>> inheritance was due to Bodhi updates, which might not go stable,
>>> if I remember correctly, but Bodhi is not in action yet I suppose,
>>> so the cut of was too soon IMO. Could you please reconsider it?
>>> Thank you.
>> No, branching is the correct time to do it. Mandated tagging through
>> koji and inheritance are completely unrelated. At the moment koji
>> tags the packages straight into f19 rather than tagging to
>> f19-updates-candidate and having bodhi deal with the tagging.
>> Inheritance only affect whether something is built in f19 is
>> inherited through to rawhide. There was a discussion some time ago
>> about this so presumably this change was either a decision by
>> release engineering or FESCo.
> I am afraid that the discussion was more generic, i.e. "Rawhide
> should not inherit from branched Fedora" and since I remember the
> main reason for breaking inheritance was Bodhi and Bodhi is not yet
> in a game, it should be clarified and adjusted.
i was asked to cut it at branching time, thats exactly what I did
Dennis, I don't blame you, but since you refer the ticket here, I can
However, this also means users using branched updates-testing get
newer packages than rawhide,
and rawhide lags behind on fixes until those updates are promoted
into updates or the base branched
repo. Sometimes this delay is quite long during freezes.
And this exact point does not apply yet and nobody realized that. I
opened new ticket for FESCo to re-evaluate it.