[haiku-development] Re: Begeistert warmup: Git migration, releases

  • From: Alexander von Gluck <kallisti5@xxxxxxxxxxx>
  • To: <haiku-development@xxxxxxxxxxxxx>
  • Date: Fri, 28 Oct 2011 15:13:12 -0500

On Fri, 28 Oct 2011 13:54:43 -0600, Alex Wilson wrote:>

Okay, back to git now... Since users would generally only be using
monthly images, we could simply tag those monthly builds.

I think something like what I have outlined above strikes a good
balance between developer productivity, git's competencies, and user
experience. Of course, I'd love to hear what others have to say,
particularily anyone else who has already been using git to work on
Haiku.



Quoting an email i sent a few months ago :)

The items below combined with an automatic monthly version update may
be just the compromise we need.

"
+1. I still like the git describe version format I commented on a few months ago: 

$ git describe --abbrev=6
6.14.1-8-g903e90
that is versiontag-hash with a shortened hash. It directs you to the code in reference to: 
 * the last major version
 * the revision

they are in order by version, and gives you the commit.
Using the odd revision numbers tags on every commit seems like trying to make 
a DVCS something it isn't =\
"

Other related posts:

  1. Home
  2. haiku-development
  3. Archive
  4. 10-2011