Please - get involved :)
General gameplan for a long time now has been to be a for user's
contributions; however with 3.0 there's a lot of room for proposing
rewrites of features and killing old APIs that aren't 'right'.
Usual 'rules' - make sure there's a JIRA for anything which is a
change to
On Fri, Aug 7, 2009 at 8:31 AM, Rahul Akolkar wrote:
> On Fri, Aug 7, 2009 at 5:09 AM, wrote:
>>
>> - "Jörg Schaible" a écrit :
>>
>>> Hi Phil,
>>>
>>> why are there still 20 issues in JIRA marked as resolved instead of
>>> closed
>>> now?
>>
>> I forgot to close them, sorry.
>> I'll do it in
Niall Pemberton wrote:
+1
Phil
I have prepared a fourth release candidate for Codec 1.4 following the
feedback from the third.
[ ] +1 Yes go ahead an release based on RC4
[ ] -1 No, because...
The tag for RC4 is here:
http://svn.apache.org/viewvc/commons/proper/codec/tags/CODEC_1_4_RC4/
The
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-jaxme has an issue affecting its community
integration
Hi gang,
is anybody fine with me getting involved with lang? I'd like to start with
committing LANG-497, a concept for Exceptions with context. We have
something like this in XStream and it is really neat to add structured
information that is not buried in plain text. Derek has provided the
implem
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-jelly-tags-fmt-test has an issue affecting its community
integrat
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-configuration-test has an issue affecting its community
integrati
