Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Message

Re: [milter-greylist] milter-greylist 3.0 alpha 5 is out

2006-09-01 by Hajimu UMEMOTO

Hi,

>>>>> On Thu, 31 Aug 2006 15:56:29 +0000
>>>>> Emmanuel Dreyfus <manu@...> said:

manu> I must confess I'm not sure I took the right decision about integrating
manu> the thread race condition fixes before the 3.0 release instead of doing
manu> it afterwards.

manu> Your work is very valuable, and I really appreciate your contribution, 
manu> but it is a huge change set. I fear it needs a lot of testing before 
manu> being ready for a release. Moreover, it fixes problems that never 
manu> appeared at mine, so that raise the question whether this huge fix was 
manu> critical enough to be merged at alpha stage. 

manu> If I made the wrong decision, it's still time to roll back. I'd like input
manu> from people that have tested previous 3.0 alpha releases: do we need the
manu> thread race condition fixes in the 3.0 release, or shall we back it out
manu> from the current sources and integrate it in the next developement release?

I don't see any thread related problem.  So, I'm not sure if it is
urgent.  However, since it changes the usage of mutex, it seems the
memory usage is greatly reduced.

manu> If the answer to this question is the second alternative, then I'll 
manu> immediatly make two releases available:
manu> 1) 3.0a6, which will be 3.0a4 plus Attila's fixes (MX sync and Tru64 build)
manu> 2) 3.1.1, which will be 3.0a5 plus your new patches.

It sounds bad choice to me.  When we have two alpha releases, it'll
make testing harder; someone will try 3.0a6 and others will try 3.1.1.
We should consider what should be in 3.0, and should be focused on
releasing 3.0, IMHO.

Sincerely,

--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
ume@...  ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.