On Thu, Apr 28, 2011 at 1:38 PM, Avram Lyon <[email protected]> wrote: > On Thu, Apr 28, 2011 at 9:35 PM, Rintze Zelle <[email protected]> wrote: >> On Thu, Apr 28, 2011 at 1:00 PM, Bruce D'Arcus <[email protected]> wrote: >>> >>> You're saying you want to fold in a backward-incompatible feature >>> addition with a bug fix release? >> >> In this context, backward-compatibility is the ability of a CSL 1.0.1 >> processor to handle CSL 1.0 styles and locales, right? Then only the bug fix >> is backward-incompatible (as defining gender-specific ordinals in the CSL >> locales will always be optional). > > I understand the importance of sticking to the versioning convention-- > so can't we say that this is 1.1.0, a new release that is primarily > intended as a bug fix release, but which is incidentally backwards > incompatible in a small way? The larger plans for 1.1 that were in the > 1-2 year range can then be moved to 1.2. It does sometime happen that > version numbers increment faster than we anticipate.
Given the way we've designed the schema (e.g. the version attribute), the 1.x releases would suggest significant changes that would require style and/or locales forks. 1.0.x releases are minor changes. I would hope we don't need to many bug fix releases, but that when we do need them, we can manage them fairly quickly. Bruce ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
