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 Oleg Kalnichevski <ol...@apache.org> on 2008/09/18 23:11:07 UTC

[mime4j] Any chance of a new release?

Folks

I think MIME4J-74 turned out to be severe enough to require a new
release rather sooner than later. There are basically two options:

(1) branch off at the 0.4 tag, fix MIME4J-74, release 0.4.1 off the
branch

(2) Alternatively we could fix some of the more important bugs out of 12
currently targeted at 0.5 [1], release 0.5 off the trunk, push less
important ones to 0.6.

Which of the two scenarios would you prefer? I am prepared to do the
necessary work and act as a RM for the new release

Oleg 

[1]
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310521&fixfor=12313178


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


Re: [mime4j] Any chance of a new release?

Posted by Robert Burrell Donkin <ro...@gmail.com>.
On 9/18/08, Oleg Kalnichevski <ol...@apache.org> wrote:
> Folks
>
> I think MIME4J-74 turned out to be severe enough to require a new
> release rather sooner than later. There are basically two options:
>
> (1) branch off at the 0.4 tag, fix MIME4J-74, release 0.4.1 off the
> branch
>
> (2) Alternatively we could fix some of the more important bugs out of 12
> currently targeted at 0.5 [1], release 0.5 off the trunk, push less
> important ones to 0.6.
>
> Which of the two scenarios would you prefer?

I need to go through the list but IIRC we fixed all bugs which could
be fixed easily and safely. If that's so, I lead towards 1.

> I am prepared to do the
> necessary work and act as a RM for the new release

Great

Robert
>
> Oleg
>
> [1]
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310521&fixfor=12313178
>
>
> ---------------------------------------------------------------------
> 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: [mime4j] Any chance of a new release?

Posted by Bernd Fondermann <be...@googlemail.com>.
On Fri, Sep 19, 2008 at 20:16, Oleg Kalnichevski <ol...@apache.org> wrote:
> On Fri, 2008-09-19 at 11:12 +0200, Stefano Bagnara wrote:
>> Oleg Kalnichevski ha scritto:
>> > Folks
>> >
>> > I think MIME4J-74 turned out to be severe enough to require a new
>> > release rather sooner than later. There are basically two options:
>> >
>> > (1) branch off at the 0.4 tag, fix MIME4J-74, release 0.4.1 off the
>> > branch
>>
>> Please remember that 0.4 shipped with a BAD NOTICE. If we branch from
>> 0.4 this HAVE TO be fixed (maybe applying r687018).
>>
>> > (2) Alternatively we could fix some of the more important bugs out of 12
>> > currently targeted at 0.5 [1], release 0.5 off the trunk, push less
>> > important ones to 0.6.
>> >
>> > Which of the two scenarios would you prefer? I am prepared to do the
>> > necessary work and act as a RM for the new release
>>
>> Current trunk has this changes from 0.4
>>
>> 687018        8/19/08 12:56 PM        1       bago    Add credit for Base64OutputStream to
>> NOTICE.txt (MIME4J-71)
>> [this should be copied to a 0.4.1 branch]
>>
>> 687784        8/21/08 5:38 PM 6       bago    Remove code copied from Apache MyFaces
>> Trinidad (Base64OutputStream & Base64OutputStreamTest). Removed NOTICE
>> credits to Oracle no more needed because of this removal. Introduced a
>> new Base64OutputStream fixed according to our test suite requirement
>> (MIME4J-71). Fixed Entity.writeTo to not append CRLF_CRLF in the base64
>> specific case (so at least this works like the qp code.
>>
>> 696072        9/16/08 11:36 PM        6       rdonkin MIME4J-72
>> https://issues.apache.org/jira/browse/MIME4J-72 Contributed by Markus
>> Wiederkehr.
>> 696237        9/17/08 1:06 PM 1       bago    MIME4J-72
>> https://issues.apache.org/jira/browse/MIME4J-72 Contributed by Markus
>> Wiederkehr. Missing Disposable interface.
>>
>> 696267        9/17/08 2:08 PM 2       niklas  Resolved issue MIME4J-74
>>
>> IMHO we should add to the list:
>> https://issues.apache.org/jira/browse/MIME4J-57
>> Add a max limit to header length for parsing.
>> https://issues.apache.org/jira/browse/MIME4J-75
>> Rename o.a.j.mj.stream to o.a.j.mj.io for test classes
>>
>> And then we should release 0.5.
>>
>
> Cool. Sounds like a plan. I am working on fixing MIME4J-57

+1 for the plan.

  Bernd

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


Re: [mime4j] Any chance of a new release?

Posted by Oleg Kalnichevski <ol...@apache.org>.
On Fri, 2008-09-19 at 11:12 +0200, Stefano Bagnara wrote:
> Oleg Kalnichevski ha scritto:
> > Folks
> > 
> > I think MIME4J-74 turned out to be severe enough to require a new
> > release rather sooner than later. There are basically two options:
> > 
> > (1) branch off at the 0.4 tag, fix MIME4J-74, release 0.4.1 off the
> > branch
> 
> Please remember that 0.4 shipped with a BAD NOTICE. If we branch from 
> 0.4 this HAVE TO be fixed (maybe applying r687018).
> 
> > (2) Alternatively we could fix some of the more important bugs out of 12
> > currently targeted at 0.5 [1], release 0.5 off the trunk, push less
> > important ones to 0.6.
> > 
> > Which of the two scenarios would you prefer? I am prepared to do the
> > necessary work and act as a RM for the new release
> 
> Current trunk has this changes from 0.4
> 
> 687018	8/19/08 12:56 PM	1	bago	Add credit for Base64OutputStream to 
> NOTICE.txt (MIME4J-71)
> [this should be copied to a 0.4.1 branch]
> 
> 687784	8/21/08 5:38 PM	6	bago	Remove code copied from Apache MyFaces 
> Trinidad (Base64OutputStream & Base64OutputStreamTest). Removed NOTICE 
> credits to Oracle no more needed because of this removal. Introduced a 
> new Base64OutputStream fixed according to our test suite requirement 
> (MIME4J-71). Fixed Entity.writeTo to not append CRLF_CRLF in the base64 
> specific case (so at least this works like the qp code.
> 
> 696072	9/16/08 11:36 PM	6	rdonkin	MIME4J-72 
> https://issues.apache.org/jira/browse/MIME4J-72 Contributed by Markus 
> Wiederkehr.
> 696237	9/17/08 1:06 PM	1	bago	MIME4J-72 
> https://issues.apache.org/jira/browse/MIME4J-72 Contributed by Markus 
> Wiederkehr. Missing Disposable interface.
> 
> 696267	9/17/08 2:08 PM	2	niklas	Resolved issue MIME4J-74
> 
> IMHO we should add to the list:
> https://issues.apache.org/jira/browse/MIME4J-57
> Add a max limit to header length for parsing.
> https://issues.apache.org/jira/browse/MIME4J-75
> Rename o.a.j.mj.stream to o.a.j.mj.io for test classes
> 
> And then we should release 0.5.
> 

Cool. Sounds like a plan. I am working on fixing MIME4J-57

Cheers,

Oleg


> 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: [mime4j] Any chance of a new release?

Posted by Stefano Bagnara <ap...@bago.org>.
Oleg Kalnichevski ha scritto:
> Folks
> 
> I think MIME4J-74 turned out to be severe enough to require a new
> release rather sooner than later. There are basically two options:
> 
> (1) branch off at the 0.4 tag, fix MIME4J-74, release 0.4.1 off the
> branch

Please remember that 0.4 shipped with a BAD NOTICE. If we branch from 
0.4 this HAVE TO be fixed (maybe applying r687018).

> (2) Alternatively we could fix some of the more important bugs out of 12
> currently targeted at 0.5 [1], release 0.5 off the trunk, push less
> important ones to 0.6.
> 
> Which of the two scenarios would you prefer? I am prepared to do the
> necessary work and act as a RM for the new release

Current trunk has this changes from 0.4

687018	8/19/08 12:56 PM	1	bago	Add credit for Base64OutputStream to 
NOTICE.txt (MIME4J-71)
[this should be copied to a 0.4.1 branch]

687784	8/21/08 5:38 PM	6	bago	Remove code copied from Apache MyFaces 
Trinidad (Base64OutputStream & Base64OutputStreamTest). Removed NOTICE 
credits to Oracle no more needed because of this removal. Introduced a 
new Base64OutputStream fixed according to our test suite requirement 
(MIME4J-71). Fixed Entity.writeTo to not append CRLF_CRLF in the base64 
specific case (so at least this works like the qp code.

696072	9/16/08 11:36 PM	6	rdonkin	MIME4J-72 
https://issues.apache.org/jira/browse/MIME4J-72 Contributed by Markus 
Wiederkehr.
696237	9/17/08 1:06 PM	1	bago	MIME4J-72 
https://issues.apache.org/jira/browse/MIME4J-72 Contributed by Markus 
Wiederkehr. Missing Disposable interface.

696267	9/17/08 2:08 PM	2	niklas	Resolved issue MIME4J-74

IMHO we should add to the list:
https://issues.apache.org/jira/browse/MIME4J-57
Add a max limit to header length for parsing.
https://issues.apache.org/jira/browse/MIME4J-75
Rename o.a.j.mj.stream to o.a.j.mj.io for test classes

And then we should release 0.5.

Stefano

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