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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
