I don't think anyone in Solr land is objecting to more frequent releases, just with a little more notice.

I wouldn't object to a release every two months... or even every month. Just give a clear notice of three freeze dates:

1. Initial Feature Freeze. Initial commit of a big new change that may take more than two weeks to stabilize, or any significant change in progress that is having stability issues or is significantly incomplete as of its latest commit. Give at least a week's notice before the "initial feature freeze", and the freeze date should be at least two weeks before branching. 2. Soft Code Freeze. Final commit before branching. At least a week before branching, and a week's notice as well. 3. Code Freeze. Final bug fix on branch for release unless blocker. Allow at least two or three days before calling a vote on the initial RC.

If Lucene (and Elasticsearch!) guys need more frequent releases, just start the process earlier.

-- Jack Krupansky

-----Original Message----- From: Robert Muir
Sent: Thursday, September 12, 2013 11:30 AM
To: [email protected]
Subject: Re: Lucene/Solr 4.5

On Sep 12, 2013, at 11:07 AM, Robert Muir <[email protected]> wrote:

The "give me several weeks to shove shit in and destabilize the
codebase" is worse.


It's a false dichotomey for a start - it's also a wild exageration.

Its no exaggeration at all. This situation actually happened to me
several times while I was release manager.


It's also a nasty judgment of your fellow committers - I see you have been
committing a lot over the past few weeks - you have just been shoving shit
in and destabilizing the code base?

How so? Did tests destabilize and start failing as a result of my
commits? No offense, but people in glass houses shouldnt throw stones.

its always the same story every time: lucene guys want more releases,
solr guys want more time for shoving. Don't try to justify it or make
it seems like its something other than what it is, because the
situation is totally clear to anyone with a working brain.

---------------------------------------------------------------------
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]

Reply via email to