before anybody jumps the gun - I am working on updateing the branch_4x version wise (uwe take it easy one thing a time :)
On Tue, Feb 18, 2014 at 11:50 AM, Simon Willnauer <[email protected]> wrote: > Folks, > > I created a release branch for 4.7 > https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_4_7 > Please backport stuff that should go into the branch until tomorrow > noon CEST. I'd appreciate if large changes could wait until 4.8 to > not unnecessarily destabilize 4.8. I will build an RC0 today to check > if something is broken, once I am done I will post the link here such > that folks can take a look at it and maybe this time it doesn't take 4 > RCs to get it done. > > > thanks, > > simon > > > On Sat, Feb 15, 2014 at 11:58 PM, Chris Hostetter > <[email protected]> wrote: >> >> : I am assuming the snapshot of the ref guide is also taken for the release, >> : so does that mean changes in ref guide has to be made before the snapshot >> : (of the release)? or is the ref guide snapshot taken seperately from the >> : release snapshot? >> >> They are done independently since they come from seperate "sources of >> truth" and as a result have seperate VOTE threads. We usually try to cut >> an RC of the ref guide just after the first RC of the code -- but there's >> no hard and fast rule aout timing. People *should* be docing things in >> the ref guide as they commit to 4x, but if voting is in progress on a code >> RC and folks want to keep working on the ref guide to polish things up >> then (in my opinion) it's worth it to delay the ref guide release a few >> days while doing so. >> >> >> -Hoss >> http://www.lucidworks.com/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
