You are probably right that we should maintain stable releases on branches (i.e. common practice). We're not doing this though :-)
All development is done on the master tree and releases are tagged. Reinier Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Nicholas Van Weerdenburg Verzonden: maandag 10 november 2008 23:16 Aan: tracks ([email protected]) Onderwerp: [Tracks-discuss] Maintenance of Tracks- No Maintenance Branches? Looking at the github repository, I see v1.6 is a tag. In my prior life, I used maintenance branches to release code in svn, so releases were on a branch and then tagged for minor revisions. What's the common practice with Git (if one) and what is Track's doing? Thanks, Nick Nicholas Van Weerdenburg Director, Product Marketing and Customer Excellence Dyadem International tel: +1.905.762.2555 fax: +1.905.762.5222 [EMAIL PROTECTED] www.dyadem.com THE INFORMATION CONTAINED IN THIS ELECTRONIC MESSAGE IS CONFIDENTIAL INFORMATION AND IS INTENDED ONLY FOR THE PERSONAL USE OF THE INDIVIDUAL OR ENTITY NAMED ABOVE. This electronic transmission may also be a Dyadem client communication that is privileged and confidential. If the reader of this message is not the intended recipient, you are hereby notified that any distribution, replication of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone or return electronic mail and delete the original message. Thank you.
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
