You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Joerg Heinicke <jo...@gmx.de> on 2004/02/06 12:10:32 UTC

Cocoon 2.0.5 release (was: Switching to licence 2.0?)

On 06.02.2004 10:07, Sylvain Wallez wrote:

>> Yes, this is a lot of work - and we have to do it on all branches where
>> we expect new releases, so it might be safer to not only change 2.1.x
>> and 2.2.x but also the 2.0.x branch.
> 
> 2.0.x? Do you really think there will be new releases in this branch?

Yes, I would also like to see a 2.0.5 release as a final step for the 
2.0 branch. After this we will only release security patches or similar. 
But much effort has been put into the 2.0 branch in the more than half 
year from the 2.0.4 and the 2.1 release. I don't want to see it lost.

But before the release we should solve the one issue with a broken batik 
JAR in 2.0:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26392

Joerg

Re: Cocoon 2.0.5 release

Posted by Steven Noels <st...@outerthought.org>.
On 06 Feb 2004, at 13:04, Joerg Heinicke wrote:

> I can wait til March :p

The re-licensing can be done before that. I looked at the Python script 
in committers/ - but the warning in the README.txt scares me a bit.

</Steven>
-- 
Steven Noels                            http://outerthought.org/
Outerthought - Open Source Java & XML            An Orixo Member
Read my weblog at            http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org                stevenn at apache.org


Re: Cocoon 2.0.5 release

Posted by Joerg Heinicke <jo...@gmx.de>.
On 06.02.2004 12:53, Carsten Ziegeler wrote:

>>>2.0.x? Do you really think there will be new releases in this branch?
>>
>>Yes, I would also like to see a 2.0.5 release as a final step for the
>>2.0 branch. After this we will only release security patches or similar.
>>But much effort has been put into the 2.0 branch in the more than half
>>year from the 2.0.4 and the 2.1 release. I don't want to see it lost.
>>
>>But before the release we should solve the one issue with a broken batik
>>JAR in 2.0:
>>http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26392
> 
> I'm not against a 2.0.5 release, and I also think that it makes sense to
> "close the branch"; but I'm not able to do a release before March. So,
> I would be very happy if someone else would do it.
> Releasing 2.0.x is much more work than 2.1 as it has binary distributions
> which have to be tested against the different jdks etc. So be warned :)

I can wait til March :p

Joerg

RE: Cocoon 2.0.5 release (was: Switching to licence 2.0?)

Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Joerg Heinicke wrote:
>
> On 06.02.2004 10:07, Sylvain Wallez wrote:
>
> >> Yes, this is a lot of work - and we have to do it on all branches where
> >> we expect new releases, so it might be safer to not only change 2.1.x
> >> and 2.2.x but also the 2.0.x branch.
> >
> > 2.0.x? Do you really think there will be new releases in this branch?
>
> Yes, I would also like to see a 2.0.5 release as a final step for the
> 2.0 branch. After this we will only release security patches or similar.
> But much effort has been put into the 2.0 branch in the more than half
> year from the 2.0.4 and the 2.1 release. I don't want to see it lost.
>
> But before the release we should solve the one issue with a broken batik
> JAR in 2.0:
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26392
>

I'm not against a 2.0.5 release, and I also think that it makes sense to
"close the branch"; but I'm not able to do a release before March. So,
I would be very happy if someone else would do it.
Releasing 2.0.x is much more work than 2.1 as it has binary distributions
which have to be tested against the different jdks etc. So be warned :)

Carsten