Bean wrote: > Hi, > > I think it could be beneficial to have a experimental branch for GRUB. > Minor bug fixes can be applied to mainstream directly. But for big and > intrusive changes, such as the new menu system, we can place it in the > experimental branch first. Users interested in the latest fancy > feature can use the experimental branch, while more conservative users > can use mainstream code. When the code in experimental branch become > stable enough, we can integrate it back to the main repository. > > I'm for this idea but we should ensure that features propagate reasonably fast from experimental to main trunk. I propose to use experimental only for features which are invasive and which may break other features or big patches which needs several stages before being usable or big patches which take too long to review. New non-intrusive developement should get quite fast to normal trunk. For experimental branches to be useful developpers should feel free to commit the code even which wasn't reviewed the only 2 rules for experimental branch should be: -No commitment of non-FSF-copyrighted code without explicit maintainer approval -Respect of others
I also propose to have some kind of version string which would identify from which experimental branch the grub was compiled and putting a warning at the end of configure script so users would exercise additional care -- Regards Vladimir 'phcoder' Serbinenko Personal git repository: http://repo.or.cz/w/grub2/phcoder.git _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
