+1 We need a freeze policy.
Like when in release cycle we freeze and what - version or release if version is freezed the release should be like x.y handled with rpmlint? Branching should be done after release of final product, and then cooker should be un-frozen, to prevent current situation: Cooker release number is not equal to 2013.0 release number Not to mention other things, patches some spec modifications. ------Oryginalna wiadomość------ Od: Crispin Boylan Nadawca: [email protected] Do: Cooker OpenMandriva Odpowiedz adresatowi: Cooker OpenMandriva Temat: Re: [OM Cooker] Un-freezing Cooker Wysłano: 9 lis 2013 21:53 On 09/11/13 20:48, Bernhard Rosenkränzer wrote: > Hi, > given everyone has been ignoring the freeze anyway and Cooker is > already totally unusable, I'd say we may as well officially un-freeze > Cooker (that, or ban almost everyone for ignoring the freeze ;) )... > > What do others think? > > ttyl > bero > > happy with that. i think it would be better if next time we freeze for a period, then branch for release and unfreeze cooker simultaneously. i'm not sure the extended 'freeze' has helped us any this time. having said that, it would be nice to actually be able to enforce the freeze! thanks cris. Wysłano z BlackBerry® w Orange
