Seems like a good idea to me. Martijn
On 6 March 2012 07:42, Shai Erera <ser...@gmail.com> wrote: > I agree. > > Maybe we should also tag issues as 4.0-alpha, 4.0-beta in JIRA? For > 4.0-alpha we'll tag all the issues that are expected to change the index > format, and 4.0-beta all the issues that require API changes? > > Shai > > > On Tue, Mar 6, 2012 at 5:20 AM, Robert Muir <rcm...@gmail.com> wrote: > >> Just thinking ahead a bit: since 4.0 will really be a pretty big >> release, we have mentioned on the list a few times the ideas of >> alphas/betas. >> I like the idea of trying to iterate towards a release here, as I >> think there will be numerous packaging and documentation issues, >> forget about >> any real bugs or API problems. >> >> I was thinking that in order to actually get people to use and test >> these things, we should try to make them more than just nightly >> builds. >> >> Here are some quick ideas: >> >> Alpha: >> We won't change the index format unless necessary to fix a bug >> >> Beta: >> We won't change public apis or configuration files unless necessary >> to fix a bug >> >> Any opinions? >> We could always add more caveats if needed, but the less the better. >> >> -- >> lucidimagination.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org >> >> > -- Met vriendelijke groet, Martijn van Groningen
