commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [Sanselan] release plan?
Date Sun, 11 Dec 2011 10:36:57 GMT
On 9 December 2011 13:53, sebb <sebbaz@gmail.com> wrote:
> On 9 December 2011 13:52, Gary Gregory <garydgregory@gmail.com> wrote:
>> On Fri, Dec 9, 2011 at 8:51 AM, Gary Gregory <garydgregory@gmail.com> wrote:
>>
>>> On Fri, Dec 9, 2011 at 8:45 AM, sebb <sebbaz@gmail.com> wrote:
>>>
>>>> On 9 December 2011 12:10, Damjan Jovanovic <damjan.jov@gmail.com> wrote:
>>>> > Hi
>>>> >
>>>> > Yes, it's time for a release. All tests now pass, and most of the
>>>> serious
>>>> > issues are now fixed.
>>>>
>>>> The tests are very "noisy" at present - there is a lot of output to
>>>> standard out, which makes it quite tricky to follow the progress of
>>>> the tests.
>>>>
>>>> The debug output should be off by default; it might however be useful
>>>> to make this switchable, rather than deleting it.
>>>>
>>>> Probably sufficient to do this per test class as a static boolean flag.
>>>> If a test case fails, one will need to go into the code anyway, so
>>>> probably not necessary to make the output externally switchable.
>>>>
>>>> Agreed?
>>>>
>>>> > However I did promise a few people their patches would get attention,
so
>>>> > first I would like to review and apply the TIFF performance enhancement
>>>> > patches by Gary Lucas (SANSELAN-56 to 58), and the TIFF G.3 and G.4
>>>> > compression patches (SANSELAN-48). Then after that, which is hopefully
>>>> > early next week, I'll start the release process.
>>>> >
>>>> > Regards
>>>> > Damjan
>>>> >
>>>> > On Fri, Dec 9, 2011 at 1:20 PM, Gary Gregory <garydgregory@gmail.com>
>>>> wrote:
>>>> >
>>>> >> Hi all,
>>>> >>
>>>> >> I've a lot of commit activity here recently which is quite welcome.
>>>> >> What are thoughts on releasing? Can anyone comment on the state
of the
>>>> >> component?
>>>>
>>>
>>> +1. Or, the tests can use log4j... which seems more civilized and reading
>>> and editing code to enable debug output.
>>>
>>
>> Or JUL for that matter.
>
> Should have read the code first - there's actually a Debug class that
> handles all the output, so it's easy to fix this.

Done.

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


Mime
View raw message