level of detail in top-level status.xml

[David Crossley <cr...@apache.org>]

We decided a while ago and reinforced it recently,
that the detailed changes about plugins go in to
the status.xml files within each plugin.

The top-level site-author/status.xml would hold stuff
related to the current core, the project as a whole,
to the tools (forrestbot, forrestbar, etc.), and also
duplicates any really important changes to the various
individual plugins, e.g.
* PhotoGallery plugin has backward-incompatible changes;
* All plugins now use the locationmap;
* Such-and-such is a new whiteboard input plugin;
etc.

When i am finished with adding some missing main
changes, then i propose to review the status file
and move the detailed changes over to each relevant
plugin/status.xml files. That is going to require
judgement calls on my part. I will try to be fair.

Thorsten, would you please add changes from here on
into the dispatcher and themes plugins. I started the
other day when i committed Brian's CSS validation patches.

If people want to revisit this decision then please
speak up ASAP.

I suppose an alternative is to completely abandon the
plugins/status.xml files. We could then prefix each
text entry with its plugin's name. Or we could have
a "context" value for each plugin.

-David

Re: level of detail in top-level status.xml

[Thorsten Scherler <th...@apache.org>]

El vie, 09-06-2006 a las 12:06 +1000, David Crossley escribió:
> We decided a while ago and reinforced it recently,
> that the detailed changes about plugins go in to
> the status.xml files within each plugin.
> 
> The top-level site-author/status.xml would hold stuff
> related to the current core, the project as a whole,
> to the tools (forrestbot, forrestbar, etc.), and also
> duplicates any really important changes to the various
> individual plugins, e.g.
> * PhotoGallery plugin has backward-incompatible changes;
> * All plugins now use the locationmap;
> * Such-and-such is a new whiteboard input plugin;
> etc.
> 
> When i am finished with adding some missing main
> changes, then i propose to review the status file
> and move the detailed changes over to each relevant
> plugin/status.xml files. That is going to require
> judgement calls on my part. I will try to be fair.
> 
> Thorsten, would you please add changes from here on
> into the dispatcher and themes plugins. I started the
> other day when i committed Brian's CSS validation patches.

Will do, when I am finished with the main status.xml.

salu2
-- 
thorsten

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)

Re: level of detail in top-level status.xml

[Ross Gardler <rg...@apache.org>]

David Crossley wrote:
> If people want to revisit this decision then please
> speak up ASAP.

I'm happy with our past decision.

> I suppose an alternative is to completely abandon the
> plugins/status.xml files. We could then prefix each
> text entry with its plugin's name. Or we could have
> a "context" value for each plugin.

I don't think this is a good idea it will bloat the core status.xml file 
unnecessarily. If we want a unified status.xml for all components we can 
provided an aggregation from within projectInfo.

Ross