On Sun, Mar 07, 2010 at 07:34:25AM -0500, Orcan Ogetbil wrote: > On Sun, Mar 7, 2010 at 6:08 AM, Michael Schwendt wrote: > > On Sat, 6 Mar 2010 20:47:40 -0500, Orcan wrote: > > > >> On Sat, Mar 6, 2010 at 8:20 PM, Rahul Sundaram wrote: > >> > On 03/07/2010 06:47 AM, Orcan Ogetbil wrote: > >> >> > >> >> Again I say "updates-testing"! Leaving php-5.3 in testing on F-11 for > >> >> a couple months will warn the users what is coming up and gives them > >> >> plenty of time to adapt. > >> >> > >> > > >> > If you have a large codebase two months is barely enough time to even > >> > big evaluating a move > >> > > >> > >> Then make it 3 months, 4 months... Leave it in testing forever if you > >> get too many complaints. But make it available for those who want it. > > > > You want to force the dist users to consider updates-testing. > > That isn't nice, and you won't be successful with such a strategy. > > > > "it is nice." is what users say, not me. I am talking as someone who > has been using this strategy for a long time now. And I claim to be > successful. On the other hand you are claiming that someone who would > do what I did will not be successful. Well, experience wins. > > So far (in the last 15 monnths or so) I have gotten many good comments > and thanks by using this strategy. I got 0 (zero) complaints about a > particular update that shouldn't go into a stable release. The only > complaints I got were about a few packages that I didn't have time to > update in stable releases. People wanted updates. > Just last night I ran into an issue with this model. Packages in updates-testing aren't available to the buildroot by default. So when you need a package in updates testing in order to build you need a buildroot override. If you have a buildroot override, you no longer have the luxury of leaving an update in updates-testing for as long as you think necessary; you have to compromise with the schedule that the dependent package wants as well. This is leaving aside the fact that our tools currently don't catch packages being sent to updates before their dependencies arrive there -- that's hopefully something that will be caught by autoqa soon. -Toshio
Attachment:
pgpqrTD5Spl78.pgp
Description: PGP signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
