Subject: Proposal: Git trial for 1.0.9 - 1.0.10
Newsgroups: gmane.lisp.steel-bank.devel
Date: 2007-08-18 15:17:47 GMT (1 year, 46 weeks, 2 hours and 33 minutes ago)
I'd propose that for 1.0.9 - 1.0.10 series we give Git a
try.
Like so:
1. Make a fork called master.git under the sbcl.git
repository on repo.or.cz, and add all committers
who want to take part in the experiment as pushers.
Committers who don't want to take part can continue
using the CVS, and I can see to pushing their CVS
commits onto master.git. (But I really hope there are
none...)
2. Change the version numbering system to use something
like the make-version.sh I just posted. I can take
care of this as well.
3. Hack, hack, hack, push push push -- but when pushing
onto master.git, don't prefix the first line of the
commit message with a version number. The commit is
already unambiguous.
4. Freeze. During the freeze commit everything from master.git
to CVS. Tag, release.
During the whole month of this, and esp. freeze we need to
decide if we want to continue using Git after this.
If yes: replace the sbcl.git with a push-repository having the
same contents (since currently the sbcl.git is the CVS mirror,
and cannot be pushed to), kill master.git, update the homepage,
continue using sbcl.git.
If no: kill master.git and do something else.
Does this sound reasonable? At the risk of saying the obvious,
I would really like all SBCL developers to say something, even
if only "I'm not going to have time for much SBCL hacking next
month, so (I don't really care | it's a bad time for me)."
Cheers,
-- Nikodemus
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/