Hi!
Spartacus now lives on github:
http://blog.s9y.org/archives/237-Sparta ... -read.html
(and fornicates to CVS)
Regards,
Garvin
Moving to GitHub.com: Call for developers - CVS/SVN affected
-
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Re: Moving to GitHub.com: Call for developers - CVS/SVN affe
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
Re: Moving to GitHub.com: Call for developers - CVS/SVN affe
Yay!garvinhicking wrote:Spartacus now lives on github: […] (and fornicates to CVS)
(Let's hope it doesn't catch anything ugly along the way.)
YL
Re: Moving to GitHub.com: Call for developers - CVS/SVN affe
I like this news ;)
I'd like to track a branch which will make my rapid deployment with chef much easier.... is it considered safe to track the (for example) 1.6 branch? I assume all new features will go to master (or a new branch)? and only bug fixes to the current releases branch? or are there no such guarantees?
Thanks!
-
I'd like to track a branch which will make my rapid deployment with chef much easier.... is it considered safe to track the (for example) 1.6 branch? I assume all new features will go to master (or a new branch)? and only bug fixes to the current releases branch? or are there no such guarantees?
Thanks!
-
Re: Moving to GitHub.com: Call for developers - CVS/SVN affe
That's the way it's planned – master is the "bleeding edge", 1.6 will be used for all 1.6.x versions to come.FishNiX wrote:I assume all new features will go to master (or a new branch)? and only bug fixes to the current releases branch?
YL