[KinoSearch] Backwards Compatibility Policy
henka at cityweb.co.za
Mon Jan 22 23:28:15 PST 2007
> Starting with version 1.0, KinoSearch will support obsolete
> features and files for one "extra" major revision. API features
> which are supported in 1.0 and deprecated in 1.x will be removed
> no sooner than 3.0. Indexes which are modified at least once
> using 2.x will be readable at least until 4.0.
That sounds sensible. It gives users time to address (and prepare for)
future compatibility issues, and reduces the pressure on you.
> This policy would be put in place as of revision 1.0, which is likely
> to be 0.20 with a few minor bugfixes after a few weeks of testing.
As an aside, will 0.20 break backwards compatibility for existing indexes?
I seem to recall that it would.
KinoSearch mailing list
KinoSearch at rectangular.com
More information about the kinosearch