On Tue, May 5, 2009 at 11:29 PM, Robin Sonefors <[email protected]> wrote: > On tis, 2009-05-05 at 23:10 +0300, Felipe Contreras wrote: >> >> Imagine someone who has been on a GNOME hiatus or is a new comer. What >> would be easier to understand? '1-2' or 'stable'? > > If I want the sources for the gedit in Gnome 2.26, cloning gedit's > repository and checking out the branch 'gnome-2-26' sounds like an > easy-to-remember way to do it. If I want the sources for gedit in Gnome > 2.24, I can probably deduce that 'gnome-2-24' sounds like a branch to > look for.
Right, 'gnome-2-24' does actually point to the latest release (2.24.3) which is good and I think all the GNOME projects should have such branches (perhaps 'gnome-2.24' instead) so it's easier to manually checkout the sources you want. But that's not in the guidelines, and it seems not even GTK+ is following that. I believe right now in order to find out all the latest stable packages for a certain GNOME release you need to use something like jhbuild. Also note that in gedit's repo 'gnome-2-22' is not even pointing to a release, so it might not even work and therefore not exactly what you want. But 'gedit-2-8' on the other hand (project-major-minor), that's what I'm suggesting to replace with 'stable'. > To more-or-less completely replace the contents of the branch 'stable' > every six months, and keep tags to those revisions to make sure they can > be retrieved and turned into their own branches if anyone wants, sounds > like branch abuse to me. That's exactly what people do with linux's repos, and I wouldn't call it abuse, it's a perfectly natural git operation. Note that you still need to create a local branch anyway: git checkout -b gedit-2-8 origin/gedit-2-8 There's not much difference to: git checkout -b gedit-2-8 GEDIT_2_8_2 -- Felipe Contreras _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
