james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Bagnara <apa...@bago.org>
Subject Re: Milestone from trunk
Date Mon, 05 May 2008 08:25:42 GMT
Bernd Fondermann ha scritto:
> On Sat, May 3, 2008 at 1:38 PM, Noel J. Bergman <noel@devtech.com> wrote:
>> Bernd Fondermann wrote:
>>
>>> Noel J. Bergman wrote:
>>  >> That sort of thinking led Stefano to push to rush out v2.3.0 over my
>>  >> objections that there was a critical memory leak.
>>  > This is an obvious attempt to discredit other committers and bring back
>>  > the old hostile atmosphere we were able to overcome lately.
>>
>>  No, it is an attempt to discredit false lines of reasoning about code
>>  quality.
> 
> Hardly. You could have chosen a different wording then, since there
> were a number of people who voted for this release. Instead you picked
> one. This is not technical. This is personal. And it weakens your
> technical reasoning.
> 
>   Bernd

The problem is not picking me in a group about something, IMHO. The 
problem is that Noel keeps repeating lies to discredit me and the code 
we wrote.

All of our interaction is in the mailing list. I'd like people to refer 
to something happened in the mailing list instead of reinventing the past.

Here is a detailed list of all the VOTEs about james 2.3.x releases on 
server-dev, who called them, when we did them:

Noel   - 2006/02/10 - [VOTE] James 2.3.0a1
Bago   - 2006/05/05 - [VOTE] James 2.3.0a2
Noel   - 2006/05/19 - [VOTE] 2.3.0a3 milestone
Noel   - 2006/06/02 - [VOTE] James 2.3.0 Beta 1
Bago   - 2006/07/06 - [VOTE] James 2.3.0b2 Release (Was: "votes" for 
next 2.3 release)
Norman - 2006/07/11 - [VOTE] James 2.3.0b3 Release
Norman - 2006/07/21 - [VOTE] James 2.3.0rc1 Release
Noel   - 2006/08/10 - [VOTE] JAMES v2.3 RC2 build posted
Noel   - 2006/09/01 - [VOTE] Release JAMES 2.3.0   >> FAILED
Noel   - 2006/09/12 - [VOTE] 2.3.0 RC3   >> FAILED
Norman - 2006/09/12 - [VOTE] 2.3.0 RC3 Again !
Norman - 2006/09/28 - [VOTE] 2.3.0 RC4   >> FAILED
Norman - 2006/09/29 - [VOTE] 2.3.0 RC4 again
Norman - 2006/10/08 - [VOTE] James 2.3.0rc5
Norman - 2006/10/19 - [VOTE] JAMES 2.3.0 final :-)
Norman - 2007/04/10 - [VOTE] JAMES 2.3.1RC1
Norman - 2007/04/25 - [VOTE] JAMES 2.3.1 (final)

Read this, and then read again Noel's message.. I forgot that Noel also 
tried to release James 2.3.0 final on 2006/09/01 (50 days before we 
finally released it). It is also really easy to open JIRA and to look 
who fixed what bugs and since what versions the bugs was open.

There is another *fact* about code quality: James 2.3.0 was the first 
release that let us to run James for more than one day without 
restarting it in cron. James 2.3.1 is the first release at all that 
allow us to run james forever without restarting it.
It seems that James PMC wasn't so warried about releasing unstable code 
when they released James 2.2.0 (FINAL) and previous with the knowledge 
that they needed a nightly restart, why are we discussing about the 
quality of a milestone without having a single proof that it doesn't work?

If needed I can provide links to message archives to prove each single 
sentence of this post.

I'd also like to thank Norman for the gigantic efforts in testing and 
preparing 2.3.x releases! It was fun to work on code and *real* bugs to 
increase the code quality. I remember we spent a lot of hours with 
James-dev code in production and debugging mine and his server to fix 
bugs. It was hard but cool. And I also thanks Noel for what he did until 
2 years ago. I prefer when he writes code.

Stefano


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message