Re: [cclib-devel] New release

[Noel O'B. <bao...@gm...>]

But this is exactly what we are doing, except that "now" for me, means
a few weeks time. I've got various excuses like grant deadlines, and a
talk to prepare, but I guess the real reason is that it doesn't seem
to be quite urgent. It takes a bit of time to prepare a release - is
there any strong reason you would like to see it out by the end of
this month, rather than next?

Noel

2008/5/21 Karol M. Langner <kar...@gm...>:
> Why not make a quick bug-fix release now (there have been quite a few
> things fixed) and concentrate on a larger release later?
>
> - Karol
>
> On Thursday 15 May 2008, Noel O'Boyle wrote:
>> Ditto. I think we are in agreement on this. Any major development
>> should be done on a branch after this point.
>>
>> Noel
>>
>> 2008/5/14 Karol M. Langner <kar...@gm...>:
>> > On Wednesday 14 May 2008, Adam Tenderholt wrote:
>> >> The regression script looks fine to me now. I wonder if it was
>> >> because I was using the trunk regression.py script while having
>> >> another branch/ tag of cclib installed.
>> >
>> > I have no problem with that regression file.
>> >
>> >> If everyone else is on board for getting a new release out at
>> >> the end of June, I'm up for it. Is this going to mainly be a
>> >> bug-fix release or are we adding significant new features? We
>> >> should probably move this discussion into a new thread.
>> >
>> > I would opt for a quick release in June that concentrates on bug
>> > fixes, and then follow up with the next major release, if we find
>> > the time and new stuff gets done.
>> >
>> > Karol
>
> --
> written by Karol Langner
> Wed May 21 11:56:12 CEST 2008
>