You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Stefano Bagnara <ap...@bago.org> on 2006/10/06 20:08:58 UTC
[POLL] 2.3.0 release plans
Hi all,
4 days ago we released James 2.3.0RC4 and we already collected 3 bugs
and fixed them:
JAMES-625 - an empty mbox will cause an error at pop3 login
https://issues.apache.org/jira/browse/JAMES-625
Critical, but only when using MBoxFileRepository (I expect other similar
bugs in less used components)
JAMES-644 - FileRegexMatcher possibly leaks minor memory on startup
https://issues.apache.org/jira/browse/JAMES-644
A minor issue: a single file descriptor is kept busy during all the
james life.
JAMES-649 - error "OutOfMemoryError: JAVA HEAP SPACE" in connections log
file when doing a POP TOP for 4000 messages
https://issues.apache.org/jira/browse/JAMES-649
Well, the fix for this is an optimisation: we now avoid to parse the
message in pop3 top calls and try to stream it directly.
---
Now we have a choice for the next step:
1) start a vote to release 2.3.0rc4 as 2.3.0 final
2) include 1 or more of the 3 patches and start a vote for 2.3.0 final
3) include 1 or more of the 3 patches and start a vote for 2.3.0rc5
4) wait few days more.
I have not a strong opinion on this, because I'm already focused on our
trunk.
My "votes" are:
1) +0.6 I would at least remove the mbox comment in config.xml
2) -0 We never followed this workflow
3) +0.4 Apply all of them
4) -0 I don't like to wait ;-)
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [POLL] 2.3.0 release plans
Posted by Guillermo Grandes <gu...@gmail.com>.
I like: 3) include 1 or more of the 3 patches and start a vote for 2.3.0rc5
+1 (all patches), IMHO when 2.3.0-final see the light, It should be...
"almost" perfect, to send 2.2 to the paper-reciclator :-)
PS: when if it is possible to be making a release each 2-3 major patches or
each 2-3 months (first to happen).
-- Guillermo
----- Original Message -----
From: "Stefano Bagnara" <ap...@bago.org>
To: "James Developers List" <se...@james.apache.org>
Sent: Friday, October 06, 2006 8:08 PM
Subject: [POLL] 2.3.0 release plans
> Hi all,
>
> 4 days ago we released James 2.3.0RC4 and we already collected 3 bugs and
> fixed them:
>
> JAMES-625 - an empty mbox will cause an error at pop3 login
> https://issues.apache.org/jira/browse/JAMES-625
>
> Critical, but only when using MBoxFileRepository (I expect other similar
> bugs in less used components)
>
> JAMES-644 - FileRegexMatcher possibly leaks minor memory on startup
> https://issues.apache.org/jira/browse/JAMES-644
>
> A minor issue: a single file descriptor is kept busy during all the james
> life.
>
> JAMES-649 - error "OutOfMemoryError: JAVA HEAP SPACE" in connections log
> file when doing a POP TOP for 4000 messages
> https://issues.apache.org/jira/browse/JAMES-649
>
> Well, the fix for this is an optimisation: we now avoid to parse the
> message in pop3 top calls and try to stream it directly.
>
> ---
>
> Now we have a choice for the next step:
> 1) start a vote to release 2.3.0rc4 as 2.3.0 final
> 2) include 1 or more of the 3 patches and start a vote for 2.3.0 final
> 3) include 1 or more of the 3 patches and start a vote for 2.3.0rc5
> 4) wait few days more.
>
> I have not a strong opinion on this, because I'm already focused on our
> trunk.
>
> My "votes" are:
> 1) +0.6 I would at least remove the mbox comment in config.xml
> 2) -0 We never followed this workflow
> 3) +0.4 Apply all of them
> 4) -0 I don't like to wait ;-)
>
>
> Stefano
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [POLL] 2.3.0 release plans
Posted by Vincenzo Gianferrari Pini <vi...@praxis.it>.
>
> Now we have a choice for the next step:
> 1) start a vote to release 2.3.0rc4 as 2.3.0 final
-0
> 2) include 1 or more of the 3 patches and start a vote for 2.3.0 final
-1
> 3) include 1 or more of the 3 patches and start a vote for 2.3.0rc5
+1
And start a vote for 2.3.0 final shortly after that, before any new bug
arises ;-) .
> 4) wait few days more.
-0
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [POLL] 2.3.0 release plans
Posted by Bernd Fondermann <be...@googlemail.com>.
On 10/6/06, Stefano Bagnara <ap...@bago.org> wrote:
> Now we have a choice for the next step:
> 1) start a vote to release 2.3.0rc4 as 2.3.0 final
+1
> 2) include 1 or more of the 3 patches and start a vote for 2.3.0 final
-1
> 3) include 1 or more of the 3 patches and start a vote for 2.3.0rc5
+0
> 4) wait few days more.
-0
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [VOTE] remove mbox repository code from JAMES 2.3
Posted by Stefano Bagnara <ap...@bago.org>.
Noel J. Bergman wrote:
> Stefano Bagnara wrote:
>> If I start a VOTE you say we should discuss it first, if I start a POLL
>> you convert a piece of it into a POLL.
>
> What happened was that I received an IM from Norman asking me if I had seen
> the mailing list today, and telling me about a vote to remove the mbox code
> because of the defects found yesterday. I didn't see a vote, so I asked him
> where. He said that the vote was in the POLL thread, hence my response. If
> this is not a vote, fine. My comments to keep the code stand.
Ok, but what's your preference between release 2.3.0rc4 as final by only
chaning the config.xml to remove the references to MBox (we don't remove
it, but only the comment so we don't add new users to the broken
implementation) and release a new rc5 with the 4 patches applied ?
>> BUT this was a poll and not a vote.
>
> As I said, a misunderstanding due to Norman's IM.
>
> --- Noel
Np, much more clear now,
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
RE: [VOTE] remove mbox repository code from JAMES 2.3
Posted by "Noel J. Bergman" <no...@devtech.com>.
Stefano Bagnara wrote:
> Noel J. Bergman wrote:
> > A POLL thread is NOT a VOTE thread.
> Of course a POLL is not a vote
> If I start a VOTE you say we should discuss it first, if I start a POLL
> you convert a piece of it into a POLL.
What happened was that I received an IM from Norman asking me if I had seen
the mailing list today, and telling me about a vote to remove the mbox code
because of the defects found yesterday. I didn't see a vote, so I asked him
where. He said that the vote was in the POLL thread, hence my response. If
this is not a vote, fine. My comments to keep the code stand.
> BUT this was a poll and not a vote.
As I said, a misunderstanding due to Norman's IM.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [VOTE] remove mbox repository code from JAMES 2.3
Posted by Stefano Bagnara <ap...@bago.org>.
Noel J. Bergman wrote:
> A POLL thread is NOT a VOTE thread. Yes, I do read all JAMES e-mail, but it
> is entirely rude to have vote threads that are not identified as such. I
> had to dig through a lot of e-mail this morning to find that there even WAS
> a vote, and only after Norman told me to look. If he hadn't have pinged me,
> I likely would not have gotten to this until tomorrow, since I'm traveling
> to ApacheCon today.
Of course a POLL is not a vote, and if you read the content of the
message the intent of this thread was not to decide wether to remove or
not this thing. I'm simply trying to understand the different positions
to be able to start a vote later.
If I start a VOTE you say we should discuss it first, if I start a POLL
you convert a piece of it into a POLL.
I really don't understand you. Ever.
Either way before making a next release I (or Norman) would have started
a vote so this is a non-problem.
>> +1 after having removed MBox class at least from the config (I don't
>> care to remove the file, my vote does not change in this regard)
>
> -1 to removing the code
>
> Absolutely not. I use that code. I have processed gigabytes worth of
> messages through that code. For two years, that code was used to process
> apache@apache.org e-mail. Yes, it appears that there are defects in store
> and with empty files, but when used to import messages from mbox
> repositories into JAMES, it works.
>
> --- Noel
BUT this was a poll and not a vote.
Since when people start a VOTE with a -1??? I never heard of such things
at ASF.
Please tell your opinion about the 2.3.0 release plan if you don't want
to make us loose too much time starting a vote that you will veto.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[VOTE] remove mbox repository code from JAMES 2.3
Posted by "Noel J. Bergman" <no...@devtech.com>.
A POLL thread is NOT a VOTE thread. Yes, I do read all JAMES e-mail, but it
is entirely rude to have vote threads that are not identified as such. I
had to dig through a lot of e-mail this morning to find that there even WAS
a vote, and only after Norman told me to look. If he hadn't have pinged me,
I likely would not have gotten to this until tomorrow, since I'm traveling
to ApacheCon today.
> +1 after having removed MBox class at least from the config (I don't
> care to remove the file, my vote does not change in this regard)
-1 to removing the code
Absolutely not. I use that code. I have processed gigabytes worth of
messages through that code. For two years, that code was used to process
apache@apache.org e-mail. Yes, it appears that there are defects in store
and with empty files, but when used to import messages from mbox
repositories into JAMES, it works.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [POLL] 2.3.0 release plans
Posted by Stefano Bagnara <ap...@bago.org>.
This news change a little my ideas and make it more "strong":
> 1) start a vote to release 2.3.0rc4 as 2.3.0 final
+1 after having removed MBox class at least from the config (I don't
care to remove the file, my vote does not change in this regard)
> 2) include 1 or more of the 3 patches and start a vote for 2.3.0 final
-1 too much changes to make a final relase without a further RC
> 3) include 1 or more of the 3 patches and start a vote for 2.3.0rc5
+0.5 including all fixes but I would anyway remove the comments about
MBoxMailRepository from the config.xml (it is for clear an untested
class so even if we fix this issue it could have many other issues and I
don't want them to block the release)
> 4) wait few days more.
-0 as before
Stefano
Norman Maurer wrote:
> Hi,
> i must add some more infos. After testing more the MBoxMailRepository i
> again found a new Bug.
> See: http://issues.apache.org/jira/browse/JAMES-655
>
> So there are 4 ways to solve this isssues for 2.3
>
> 1) Fix in 2.3 branch
> +0.8
>
> 2) Remove it from 2.3 branch
> +1
>
> 3) Hide configuration from 2.3
> +0.2
>
> 4) Fix not in 2.3
> -1
>
> Bye
> Norman
>
> Bernd Fondermann schrieb:
>> On 10/6/06, Stefano Bagnara <ap...@bago.org> wrote:
>>> Now we have a choice for the next step:
>>> 1) start a vote to release 2.3.0rc4 as 2.3.0 final
>>
>> +1
>>
>>> 2) include 1 or more of the 3 patches and start a vote for 2.3.0 final
>>
>> -1
>>
>>> 3) include 1 or more of the 3 patches and start a vote for 2.3.0rc5
>>
>> +0
>>
>>> 4) wait few days more.
>>
>> -0
>>
>> Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [POLL] 2.3.0 release plans
Posted by Guillermo Grandes <gu...@gmail.com>.
This feature make James inter-operate with other software that only read
mboxes, I think this is important.
> 1) Fix in 2.3 branch
+1
> 2) Remove it from 2.3 branch
-1 (ufff, remove is the only thing that I can't see. like a crab, walking
backwards?!? noooooo.
> 3) Hide configuration from 2.3
+0 (hide in 2.3.0final, but try correct in 2.3.1 as soon as posible)
> 4) Fix not in 2.3
-0 (not fix in 2.3.0final, but try correct in 2.3.1 as soon as posible)
I can't see good to remove a thing that is in use by people or make James
compatible with other softwares.
bye,
Guillermo
----- Original Message -----
From: "Norman Maurer" <nm...@byteaction.de>
To: "James Developers List" <se...@james.apache.org>
Sent: Saturday, October 07, 2006 2:28 PM
Subject: Re: [POLL] 2.3.0 release plans
> Hi,
> i must add some more infos. After testing more the MBoxMailRepository i
> again found a new Bug.
> See: http://issues.apache.org/jira/browse/JAMES-655
>
> So there are 4 ways to solve this isssues for 2.3
>
> 1) Fix in 2.3 branch
> +0.8
>
> 2) Remove it from 2.3 branch
> +1
>
> 3) Hide configuration from 2.3
> +0.2
>
> 4) Fix not in 2.3
> -1
>
> Bye
> Norman
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [POLL] 2.3.0 release plans
Posted by Norman Maurer <nm...@byteaction.de>.
Hi,
i must add some more infos. After testing more the MBoxMailRepository i
again found a new Bug.
See: http://issues.apache.org/jira/browse/JAMES-655
So there are 4 ways to solve this isssues for 2.3
1) Fix in 2.3 branch
+0.8
2) Remove it from 2.3 branch
+1
3) Hide configuration from 2.3
+0.2
4) Fix not in 2.3
-1
Bye
Norman
Bernd Fondermann schrieb:
> On 10/6/06, Stefano Bagnara <ap...@bago.org> wrote:
>> Now we have a choice for the next step:
>> 1) start a vote to release 2.3.0rc4 as 2.3.0 final
>
> +1
>
>> 2) include 1 or more of the 3 patches and start a vote for 2.3.0 final
>
> -1
>
>> 3) include 1 or more of the 3 patches and start a vote for 2.3.0rc5
>
> +0
>
>> 4) wait few days more.
>
> -0
>
> Bernd
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
> !EXCUBATOR:1,45277dca53071672310282!
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
RE: [POLL] 2.3.0 release plans
Posted by "Noel J. Bergman" <no...@devtech.com>.
Stefano Bagnara wrote:
> 4 days ago we released James 2.3.0RC4 and we already collected 3 bugs
> and fixed them:
> JAMES-625 - an empty mbox will cause an error at pop3 login
> https://issues.apache.org/jira/browse/JAMES-625
Apparently, hardly anyone is using mbox this way, else we'd have had a bug
report. If we release it, who would test it (other than us)? But then
again, what's the risk?
> > JAMES-644 - FileRegexMatcher possibly leaks minor memory on startup
> > https://issues.apache.org/jira/browse/JAMES-644
Worth fixing, but I agree that it is minor.
> JAMES-649 - error "OutOfMemoryError: JAVA HEAP SPACE" in connections log
> file when doing a POP TOP for 4000 messages
> https://issues.apache.org/jira/browse/JAMES-649
This one seems the only reason for RC5. And it would get a workout from
everyone who tests the RC.
I suppose RC5 would be OK. I'd like to see us post it by Monday, and plan
to release 2.3 next weekend, if there are no further problems.
Regarding the memory leak, I'll take time over the next couple of days to
see if I can isolate the error. Looking at the code for dnsjava, I don't
see any separate Cache in the lookup code other than for DClass.IN.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org