Thanks. It's a good article that I hadn't seen yet. Part of my candidate work flow below was borrowed from reading their earlier posts and looking at their configure script.
There are gaps still though. They have an odd model though in that they don't do discrete releases of software- they commit to edge and when it looks table, move it to master. It's a continuous release process, and there is to versions at all. They also assume that you want to always be working off edge, and staying reasonably up to date. With Tracks, my wishes are a bit unique- run the stable released version and create my contributions against that. Because I'm using Track's as my life management system, I want to make sure I'm running stable code. But to encourage my coding, I'd like to deploy and test against my real-life environment (a clone of it, with deployment after testing). To use my changes quickly is a big motivation factor for me, especially considering my very little free time. If I worked on the master head, I'd never get to use my changes and still stay on a stable releases branch. Thanks, Nick -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: November 11, 2008 5:17 AM To: Nicholas Van Weerdenburg Cc: tracks ([email protected]) Subject: Re: [Tracks-discuss] Deploying Tracks Using Git to Joyent Shared Accelerator On 10 Nov 2008, at 22:13, Nicholas Van Weerdenburg wrote: > -fork main tracks repository on github > -git clone my github fork to my development box > -git clone my github cfork to my joyent account for deployment > -joyent: branch tag v1.6 to "development".. via "git co v1.6 -b > development" (is this correct, and is it doing what I expect?) > -run on this > -development box: branch tag v1.6 to "development". > -commit changes to "development" branch on my github > -pull from there to my joyent clone > -when wanting to patch, merge from development to master on github > and do a pull request. This article: http://blog.insoshi.com/2008/10/14/setting-up-your-git-repositories-for-open-source-projects-at-github/ has some good advice for how to set up open source projects so that you can maintain a stable branch for your own use, do some hacking and contribute those changes back to the project. cheers, bsag -- but she's a girl - the weblog of a female geek http://www.rousette.org.uk [EMAIL PROTECTED] _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
