On Fri, Jul 20, 2012 at 9:30 AM, Rintze Zelle <[email protected]> wrote: > On Thu, Jul 19, 2012 at 5:40 PM, Sylvester Keil <[email protected]> > wrote: >> >> Another question we should keep in mind whether it may not be easier to >> work on the master branch and have separate release branches? Especially if >> we may want to keep separate versions of styles in the future (i.e., 1.0 >> branch, 1.0.1 branch). > > > Yes, it might be better to always commit to "master" and push updates from > there to a branch for the most recent CSL version (now "1.0", soon "1.0.1") > (I'm not sure we need to maintain styles for older CSL versions). That way > consumers of CSL styles such as Zotero can just pick a branch (e.g. "1.0"), > and upgrade when they're ready. That will especially help once we have a big > non-backward compatible upgrade, similar as what we had when we went from > CSL 0.8.1 to 1.0. > > Rintze
Committing to version branches (1.0, 1.0.1, 1.1) would be simpler to explain. Style maintainers could then just check changes in on the branch of the style they have to hand, and Travis magic can work out whether it's a branch to which fast-forwarding in master applies etc. Frank ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
