Calling all regressions

[Bron Gondwana]

On Tue, Mar 10, 2009 at 01:33:00PM -0400, Wesley Craig wrote:
> On 10 Mar 2009, at 08:51, Michael Menge wrote:
> > I think i should rephrase my question.
> >
> > Is there a way for cyrus to know that it was updated
> > since the last time it did run, so it can do the things
> > suggested by Bron.
> 
> Perhaps we should add a config option with no default whose value  
> must be the version of the software you're running.

Hmmm.... v2.3.13-fmsvn18309-5c1c69c4 ;)  It makes inplace updates
a cow, since cyrus detects the new file and automatically closes
old processes and starts new ones.  Pretty tricky.

Though a configuration with no default that said "running Cyrus 2.3
series" would be reasonable.

Actually, I think at this point I would recommend releasing
Cyrus 2.4 based on our current stable plus this change, and
require a config variable that said "I'm running Cyrus 2.4".

At this point I would also recommend revisiting EVERY config
option and making the default be the best value (in our humble
opinions) rather than the backwards compatible one.  I have
written about this before - and I think it's a jump we should
take pretty soon, to get all new users using the best possible
options without having to maintain a giant config file.

Bron.