----- Original Message ----- > On Mon, Mar 04, 2013 at 07:18:04PM +0100, Miloslav Trmač wrote: > > Some of the things we want to achieve: > > * Make rawhide to be reliably installable and usable by developers > > by > > coherently introducing changes. > > Another factor is that on Fedora, it seems that it is ok to break > Rawhide. At Mageia that is totally unacceptable. If it happens > accidentally, ok, but very frowned upon if you just push changes you > know might cause issues. Various things are done for those: test > some changes yourself (when it seems needed), announce possible > problems > on the mailing list, push some changes to a special testing > repository > (to get more people to test your changes other than just you). This is really what we would like to achieve - not to have Rawhide to break stuff but to work on next releases (and even not only on the next releases but upstreams etc., where you need latest bits). One of the ideas is to have merge windows for Rawhide, doing as much changes as possible in side repositories (coprs?)/branches and merge in a specific time, with the acceptance test as proposed in this revamp. That's the question on our infrastructure, how it would be possible (from dist-git, autoqa, build infra).... Jaroslav > -- > Regards, > Olav > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
