On Tue, Jul 24, 2012 at 7:21 PM, Bruce D'Arcus <[email protected]> wrote:
> Yeah, just to clarify, I thought we had previously agreed on plans for
> versioning, which effectively meant that we'd only consider style branches
> for major point releases.
>
CSL 1.0.1 will be backward compatible, but won't be forward compatible.
I.e., any valid CSL 1.0 style should work correctly with a CSL 1.0.1
processor, but a CSL 1.0.1 style won't necessarily render correctly in a
CSL 1.0 processor.
Take for instance the new "available at" term. CSL 1.0 clients that have
shipped with CSL 1.0 locales won't have that term in their locale files,
and any CSL 1.0.1 style that calls this term will at best render an empty
string (unless that style happens to define the term with cs:locale).
Another example is the Zotero Style Repository. If we introduce styles with
CSL 1.0.1 features in the "master" branch, these styles will appear to be
invalid in the Zotero Style Repository. Things would be much more robust if
Zotero could just pull their 1.0 styles from a "1.0" branch, and move
branches once they're ready for "1.0.1".
And, as you said above, branch are light-weight.
Rintze
------------------------------------------------------------------------------
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
