You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Ross Gardler <rg...@apache.org> on 2005/12/13 10:31:10 UTC
Re: svn commit: r356401 - /forrest/trunk/site-author/status.xml
thorsten@apache.org wrote:
> Author: thorsten
> Date: Mon Dec 12 14:27:07 2005
> New Revision: 356401
>
> URL: http://svn.apache.org/viewcvs?rev=356401&view=rev
> Log:
> added recent work to status
>
> Modified:
> forrest/trunk/site-author/status.xml
...
> + <action dev="TS" type="add" context="code"> Added first implementation of
> + the dispatcher. Including contract bean implementation and interface;
> + dispatcher exception and dispatcher transformers. </action>
I think we should keep status stuff for plugins in the plugins status
file rather than in the core Forrest status.file, especially when the
functionality is in the whiteboard.
However, I also think we should create another changes page that
highlights the important changes in all of the plugins. This way people
interested in the cutting edge can see, at a glance, what is happening.
Comments?
Ross
Re: svn commit: r356401 - /forrest/trunk/site-author/status.xml
Posted by Cyriaque Dupoirieux <Cy...@pcotech.fr>.
Ross Gardler a écrit :
> thorsten@apache.org wrote:
>
>> Author: thorsten
>> Date: Mon Dec 12 14:27:07 2005
>> New Revision: 356401
>>
>> URL: http://svn.apache.org/viewcvs?rev=356401&view=rev
>> Log:
>> added recent work to status
>>
>> Modified:
>> forrest/trunk/site-author/status.xml
>
>
> ...
>
>> + <action dev="TS" type="add" context="code"> Added first
>> implementation of + the dispatcher. Including contract bean
>> implementation and interface; + dispatcher exception and
>> dispatcher transformers. </action>
>
>
> I think we should keep status stuff for plugins in the plugins status
> file rather than in the core Forrest status.file, especially when the
> functionality is in the whiteboard.
>
> However, I also think we should create another changes page that
> highlights the important changes in all of the plugins. This way
> people interested in the cutting edge can see, at a glance, what is
> happening.
>
> Comments?
+1,
>
> Ross
>
>
manage our project Changes notes (Was: svn commit: r356401)
Posted by David Crossley <cr...@apache.org>.
Ross Gardler wrote:
> >Author: thorsten
> >Date: Mon Dec 12 14:27:07 2005
> >New Revision: 356401
> >
> >URL: http://svn.apache.org/viewcvs?rev=356401&view=rev
> >Log:
> >added recent work to status
> >
> >Modified:
> > forrest/trunk/site-author/status.xml
>
> ...
>
> >+ <action dev="TS" type="add" context="code"> Added first
> >implementation of + the dispatcher. Including contract bean
> >implementation and interface; + dispatcher exception and dispatcher
> >transformers. </action>
>
> I think we should keep status stuff for plugins in the plugins status
> file rather than in the core Forrest status.file, especially when the
> functionality is in the whiteboard.
>
> However, I also think we should create another changes page that
> highlights the important changes in all of the plugins. This way people
> interested in the cutting edge can see, at a glance, what is happening.
>
> Comments?
Agreed. Perhaps we can manually add some very high-level
seriously important plugins entries to the top-level
Changes.
As well, we can generate a list from the various
plugins status.xml using the "importance" attribute.
-David