cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <>
Subject Re: [C2]: Preparing the next releases
Date Fri, 08 Jun 2001 10:12:53 GMT
Quoting Carsten Ziegeler <>:

> Hi,
> wow - we did a beta 1 release and all of us survived...
> I promise that the next release of C2 will be with less
> problems.

Propabbly we all learn by doing :) 

> To keep on this great project, I think we should make 
> a simple plan for the next beta and the release:
> We should collect the things to be done for the release and
> try to make most of it into the beta 2.
> So what should be done?
> Apart from more documentation and bug fixes I would propose 
> the following changes/additions:
> - Add all changes to changes.xml so that everyone can see
>   what has changed since the beta1.

+1. I've had private mail conversation with Berin about automate release 
production as much as possible (using 
as a starting point for a guide line). This should include a standard 
announcement mail with the project description to be sent to a list of defined 
audience (anouncements lists, user lists, etc.) including the change log (since 
the last release) as well as links to important resources like the website 
and the distribution diretory etc.

> - Remove the X/CIncludeSAXConnector and use the corresponding
>   transformers instead.
> - Add an example for a SAXConnector (I am currently working
>   on a LoggingSAXConnector)

Not sure what it's worth for. Do you know the LogTransformer?

> - Decide if we want the cocoon: context in 2.0 or 2.1 (The
>   introduction *could* change some interfaces)

We had it half way working with the X/CIncludeSAXConnectors so I'd like to see 
it in 2.0 rather than 2.1, therefor +1 for 2.0

> As it seems that there is not so much to do, I would propose
> a date in the middle of July as a release date for the beta 2.


> I think we should keep the 2.1 and the 2.0 branch in sync
> until the final release of 2.0. So we could avoid the
> joining of the branches upto that point.

See my mail about that.

> Should we start bugzilla for bug reports?

Bugzilla is setup for C2 and I've made bug owned by so 
that we should get mails when new bug reports are created (tested right away, 
lets see if it will show up here)

> Other points? Suggestions? Comments?

I have still the proposal and samples from Michael Homeijer concerning C2 act as 
a SOAP client and server which is something that is really interesting to me. As 
it is nothing that would change interfaces I'd like to integrate it into 2.0. 
Any comments about it?


To unsubscribe, e-mail:
For additional commands, email:

View raw message