On 31/01/12 01:44, Kevin Kofler wrote:
> Matthias Runge wrote:
>> Maybe introducing a "testing"-release as concession to both sides is
>> acceptable?
>>
>> - newest versions, including risk of being broken -> rawhide
>> - (merely) stable versions will be propagated from rawhide to "testing"
>> - branching stable versions each six months (or so) from testing-branch
>
> No.
>
> * It's extra work to maintain the extra branch: Who would decide when a
> package is stable enough for testing? Most likely, the maintainer, who would
> then have to deal with Bodhi for testing as well, in addition to doing it
> for the releases. Having to work with Bodhi for Rawhide builds is a non-
> starter, it's already enough of a PITA to do it for the branched release. We
> cannot get any development done that way.
>
> * As I already pointed out elsewhere in the thread, branching stable from
> testing rather then Rawhide would mean older software in stable. We are not
> Debian, we want to ship current software!
>
> So no, I don't see the Debian model working for us, at all, and I don't
> consider that an acceptable compromise at all.
>
> Kevin Kofler
>
You're right, putting a testing line between rawhide and stable makes
software in stable a little older. Nobody said, packages in testing
should stay there as long as in debian-testing.
Let users decide, if something goes from rawhide to testing; take a
limit of 3 days to stay in rawhide, before it's allowed for testing.
Three days should prevent major breakages.
I know, this is kind of strict and burdens more work to maintainers.
Building in this model into bodhi could automate almost everything of it.
If we take your model (if I remember right): everybody is allowed to
submit everything in every branch may lead to some instable systems.
This model can't prevent breakage in any branch. I'd say: it provokes
breakage. I'm pretty convinced, nobody wants to break something.
Ignorance, even through no ones fault will do easily harm here.
--
Matthias Runge <mrunge@xxxxxxxxxxxxxxxxx>
<mrunge@xxxxxxxxxxxxxxxxx>
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
