Maybe beta RC's would fit the same need as additional alpha releases. Maybe
a new beta RC every week or two as significant changes accumulate would
satisfy user needs.
Maybe the real value in having an alpha release is not the release itself
(since nightly builds are readily available) but to publically mark the
milestone that development is now mostly complete and to signal
less-sophisticated users that they can now feel confident to begin serious
evaluation and that the clock is finally ticking down to a final release.
Meanwhile, more-sophisticated users can continue with nightly or local
builds as they always have.
One other question is whether the formal alpha release would "raise the bar"
for changes other than index changes. The 4.0 wiki indicates that
"additional features & API changes" would be permitted after the alpha,
suggesting a rather low bar. If there are such changes, I would argue for
more/earlier beta RCs to get user feedback on significant changes. Once
again, more-sophisticated users can access nightly builds anyway, so it is
more a matter of raising public awareness.
An early alpha and early beta RC could benefit users whose IT management
"policy" might be to avoid alpha releases and wait for beta (RC).
-- Jack Krupansky
-----Original Message-----
From: Robert Muir
Sent: Sunday, June 10, 2012 11:28 AM
To: [email protected]
Subject: Re: VOTE: Lucene/Solr 4.0-ALPHA
On Sun, Jun 10, 2012 at 11:22 AM, Jack Krupansky
<[email protected]> wrote:
So, I would suggest that there be a series of alpha releases (and betas)
as
significant bug fixes and improvements accumulate.
I won't do this. Someone else can if they want. Releasing is too
time-consuming, you dont just press a button.
--
lucidimagination.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]
