On Tue, Jan 10, 2012 at 12:50 PM, Rintze Zelle <[email protected]> wrote: > On Tue, Jan 10, 2012 at 12:13 PM, Charles Parnot <[email protected]> > wrote: >> >> So if other implementations are fine too, then we could maybe switch to >> 1.0.1 for validation. > > > My main reservation is that I pushed for some new features for CSL 1.0.1 > that are in the trunk schema and spec (and in most cases supported by > citeproc-js), but which haven't received a lot of review from the other CSL > developers/implementors, so CSL 1.0.1 final might look a bit different. So > until we release CSL 1.0.1 I'd like to hold off on adding styles to the repo > with 1.0.1 features. > > We could move to a more agile development track, where we green light and > implement features on a case-per-case basis, but that's another discussion.
Maybe instead of adding new features on trunk (well, really master; trunk is CVS/SVN language), maybe we ought to do those on branches? Features then get merged to master whenever they get cleared by X number of developers, without any objections? Bruce ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
