reservation locks [was: bogofilter-0.96.2 ...]

David Relson relson at osagesoftware.com
Sun Oct 9 14:49:02 CEST 2005


On Sun, 09 Oct 2005 08:55:09 +0200
Matthias Andree wrote:

> David Relson wrote:
> > On Thu, 6 Oct 2005 19:57:36 +0200
> > Torsten Veller wrote:
> > 
> > 
> >>* David Relson <relson at osagesoftware.com>:
> >>
> >>>Bogofilter 0.96.2 has been promoted from Current to Stable status.
> >>>
> >>>0.96.2	2005-10-06 - promoted to stable
> >>>        2005-09-25 (a.k.a. 1.0.0-rc2)
> >>
> >>Why isn't it 1.0? What is missing? What is planned?
> > 
> > 
> > Good question!
> > 
> > Matthias is planning some new reservation lock code and is strongly
> > against a 1.0 version 1.0 until it's in place.  Unfortunately he's in
> > Taiwan for the next 2 weeks.  
> > 
> > The present version bogofilter is doing great, even without the
> > additional code.  If he can get the code in without much additional
> > delay, i.e. being in Taiwan, it'll become 1.0rc3.  If the new code
> > won't be available soon, I'm inclined to release the current code as
> > 1.0 and let reservation locks go into 1.0.1.
> 
> I'm not away from my mail though, so here goes: I will certainly not 
> commit any features to the 1.0.X branch - bugfixes only. This feature 
> would then go into the development code that leads up to 1.1.0.

Hi Matthias,

How's Taiwan?

It sounds like you're suggesting reservation locks be held until
1.1.0.  Or are you saying that only the only differences between 1.0.0
and 1.0.x should be patches and any new features should bump the minor
version level, i.e. to 1.1.0?

Regards,

David



More information about the Bogofilter mailing list