You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Carsten Ziegeler <cz...@s-und-n.de> on 2002/12/06 14:26:19 UTC
[PROPOSAL]: Moving todo and tracking items
Hi,
I would propose to move the todo.xml into the docs section,
perhaps in the "plan" directory - so we have everything
for release planning in one place.
I also suggest that we start/continue adding items
into these documents so we can better coordinate a new
release, like the upcomming 2.1 release.
Carsten
Carsten Ziegeler
Open Source Group, S&N AG
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [PROPOSAL]: Moving todo and tracking items
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Nicola Ken Barozzi wrote:
>
> Carsten Ziegeler wrote:
> > Hi,
> >
> > I would propose to move the todo.xml into the docs section,
> > perhaps in the "plan" directory - so we have everything
> > for release planning in one place.
> >
> > I also suggest that we start/continue adding items
> > into these documents so we can better coordinate a new
> > release, like the upcomming 2.1 release.
>
> In Forrest we are starting to use status.xml for it.
> It contains changes, todos, action items, votes, and compatibility issues.
>
> It's basically an xml version of the STATUS document that projects
> should all be using as per charter. We are currently experimenting with
> the DTD while we use it, maybe that would solve your need of a central
> place for project&release planning.
>
Sounds good!
Carsten
Carsten Ziegeler
Open Source Group, S&N AG
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [PROPOSAL]: Moving todo and tracking items
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Carsten Ziegeler wrote:
> Hi,
>
> I would propose to move the todo.xml into the docs section,
> perhaps in the "plan" directory - so we have everything
> for release planning in one place.
>
> I also suggest that we start/continue adding items
> into these documents so we can better coordinate a new
> release, like the upcomming 2.1 release.
In Forrest we are starting to use status.xml for it.
It contains changes, todos, action items, votes, and compatibility issues.
It's basically an xml version of the STATUS document that projects
should all be using as per charter. We are currently experimenting with
the DTD while we use it, maybe that would solve your need of a central
place for project&release planning.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org