On 01.11.2011 Grant Ingersoll wrote: > FWIW, in Lucene, we do the following: > > 1. All minor versions within a major release can read prior versions index > within the same major release. That is, 3.4 can read a 3.3 index. > However, 3.3 cannot read a 3.4 index. When a user reads a 3.3 index w/ > 3.4, it is silently upgraded to 3.4. I think this versioning scheme > should work well for us to when it comes to models. In the new 4.x line, > we have a Codec system which will make it fairly easy for any version to > read any other version. > > 2. For APIs, we typically mark things as @lucene.experimental if we think > they may change within minor releases. We also mark things as deprecated > that are going away. Deprecated items are then removed on the next major > release. The upgrade path is usually to go to x.9, remove all > deprecations and then go to x+1.0. > > We also communicate to users via release notes when we purposefully broke > back compat.
Sounds all good to me. +1 Isabel
signature.asc
Description: This is a digitally signed message part.
