On Wed, Sep 19, 2007 at 08:04:16PM +0200, Thorsten Leemhuis wrote: > On 19.09.2007 19:41, Till Maas wrote: > > On Mi September 19 2007, Luke Macken wrote: > >> pushed for in the New Update Form -- which will let us remove the release > >> dropdown[0], and auto-complete *only* builds that *can* be pushed for that > >> specific release. > >> I wanted to run this by everyone, to avoid any OMGWTFREGRESSION!1 emails, > >> and to see if anyone has any comments/suggestions/oppositions. > > Imho there should be also a way to createa an update for two releases at once. > > E.g. when Fedora 8 is out, and a package is updated for it, often there will > > be the same update for Fedora 7. It seems that this was easier possible with > > the old interface, because one should be able to just go back and change the > > release and the build, but keep the bugs / cves and notice. But for a > > complete support of "identical" updates for two releases, I guess there needs > > to be changed a lot more, anyway, e.g. when one wants to edit both updates. > > While I agree in general to make stuff easier: Wouldn't it be better to > normally ship the F7 update some days after shipping the one for F8 (and > that itself some days after it hit devel)? > > That IMHO has a important benefit: if a crucial bug made it into F8 > because it was not noticed in devel or updates-testing earlier there is > still time left to *not* ship that update for F7. Agreed. Stuffing multiple releases into a single update would make the whole karma/updates-testing thing painful. Maybe the best solution is to make it trivial to "clone" an update for another release ? Or we could have the form automatically clone the update for each release based on the provided builds ? luke -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
