On Thu, Feb 15, 2018 at 11:19:10PM +0000, Sérgio Basto wrote: > On Thu, 2018-02-15 at 16:39 -0600, Rex Dieter wrote: > > Matthew Miller wrote: > > > > > As shown at https://www.happyassassin.net/nightlies.html, we > > > haven't > > > had a successful compose for almost two weeks. AIUI this is mostly > > > worked out now, but it raises the question: who should be keeping > > > track > > > of this and coordinating fixes? > > > > ... > > > What do you think? > > > > Having a rawhide coordinator (aka herder-of-cats) is an excellent > > idea. > > > Branch more earlier , 2 months without branch ok , but 5 no, is > stretching too much . Some software have 3 months cycle , so after one > soname bump on beginning of rawhide , now we a second soname bump > before branch. > > Another idea , is classify packages by importance not just in critical > path or not, at least 3 or 4 levels, where level 1 just can be > "upgraded" in an early rawhide and level 4, 5, or 6 can be upgraded > anytime and in any branch . Those are interesting ideas, but I don't see how that would make composing rawhide more successful. Mind expanding what you have in mind? I may just be missing it :) Thanks, Pierre _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
