On Tue, Dec 20, 2011 at 2:11 PM, Sebastian Karcher <
[email protected]> wrote:

> > This raises a point about our way of handling releases though. If we
> could
> > be confident that CSL processors wouldn't break by new elements and/or
> > attributes, we could move to a more fluid release schedule where features
> > can be added to styles in the repo once consensus has been reached to
> > include those features into the next CSL release.
>
that would be very useful - the status quo is a little unsatisfactory,
> because we also don't have a good way of tracking styles where
> features (I'm mainly thinking of delimiter-precedes-et-al right now)
> need to be added in the future - I know there are a bunch of styles
> with that requirement but I wouldn't know how to track them down
> easily right now - much easier if it could have been just
> implemented...
>

We would need confirmation from at least Frank (citeproc-js), Charles
(Papers2 CSL processor), Sylvester (citeproc-rb) and Andrea (citeproc-hs)
that such a change in our release workflow won't give problems, though.
(are there any other CSL processors used in production settings that I
missed?)

Rintze
------------------------------------------------------------------------------
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

Reply via email to