Moving to GitHub.com: Call for developers - CVS/SVN affected

garvinhicking
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

Post by garvinhicking »

Hi!

Spartacus now lives on github:

http://blog.s9y.org/archives/237-Sparta ... -read.html

(and fornicates to CVS)

Regards,
Garvin
# 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/
yellowled
Regular
Posts: 7111
Joined: Fri Jan 13, 2006 11:46 am
Location: Eutin, Germany
Contact:

Re: Moving to GitHub.com: Call for developers - CVS/SVN affe

Post by yellowled »

garvinhicking wrote:Spartacus now lives on github: […] (and fornicates to CVS)
Yay! :mrgreen:

(Let's hope it doesn't catch anything ugly along the way.)

YL
FishNiX
Regular
Posts: 40
Joined: Sun Sep 02, 2007 6:32 pm

Re: Moving to GitHub.com: Call for developers - CVS/SVN affe

Post by FishNiX »

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!
-
yellowled
Regular
Posts: 7111
Joined: Fri Jan 13, 2006 11:46 am
Location: Eutin, Germany
Contact:

Re: Moving to GitHub.com: Call for developers - CVS/SVN affe

Post by yellowled »

FishNiX wrote:I assume all new features will go to master (or a new branch)? and only bug fixes to the current releases branch?
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.

YL
Post Reply