forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <cross...@apache.org>
Subject Re: rearrange Components in Jira Issue Tracker
Date Sun, 31 Oct 2004 01:31:07 GMT
Dave Brondsema wrote:
> David Crossley wrote:
> > Now is a good time to rearrange our Component names.
> > Here is my first proposal. Please tweak or propose
> > something else.
> > 
> > --------------------------
> > Building Forrest ................... Build
> > shbat distribution - Forrest CLI ... Shell (command-line)
> > Forrest live webapp (Jetty) ........ Run (Jetty webapp)
> > Forrest skins ...................... Skins
> > Forrest website .................... Documentation and Website
> > .................................... Forrestbar
> > Forrestbot ......................... Forrestbot
> > XML grammars & validation .......... XML grammars & validation
> > .................................... Plugin: IMSManifest
> > .................................... Plugin: OpenOffice.org
> > .................................... Plugin: Simplified Docbook
> > Core operations .................... No Component
> > Other .............................. No Component
> > --------------------------
> > 
> 
> Why did you remove "Core operations"?  I think lots of things (e.g. 
> wholesite, or image location problems) would fit there and would be 
> difficult to place into another category.

When i viewed the issue list for that category,
it seemed like a dumping ground. So i thought
that "No Component" means the same thing.

I suppose that if we have a more complete list
of components, then "Core operations" makes sense
again (though i would like to find a better name.

> Should we have a WAR component also?

Yes, i intended to add it, but forgot.

> Does "Shell (command-line)" refer to running forrest to generate static 
> pages?  Or the .sh/.bat scripts?  Perhaps we need a category for both.

The former. Again i had trouble thinking of a
good name for it. I also wondered if we actually
need those two categories. The issues would belong
in the other categories.

Perhaps we only need components for the launching of
the three "run" situations.

.... Launch command-line
or
.... Launch 'forrest'

.... Launch local webapp
or
.... Launch 'forrest run'

........ :-) Launch war (.... no, no more bushfires :-)
.... Launch servlet WAR

> We probably should have a general plugins component also, which would 
> cover issues affecting all plugins (the pluging structure in general).

Yes.

> We should also have a component called "tools" to correspond the 
> forrest/tools/* packages.  Perhaps we could break it out more into Tool: 
> XXE, Tool: Eclipse, etc.

Okay.

The "No Component" entry is the Jira default.
In the list of components when doing "Create Issue",
that shows as the "Unknown" option.

In the current version of Jira, the issues are sorted
alphabetically only, with "Unknown" at the top.

Here is the current proposal ...

Maximum about 25 characters ........ 1234567890 1234567890 123
--------------------------
Other .............................. No Component
Core operations ....................... [not yet decided]
Building Forrest ................... Build
Forrest website .................... Documentation and Website
.................................... Forrestbar
Forrestbot ......................... Forrestbot
.................................... Forrestdoc
shbat distribution - Forrest CLI ... Launch 'forrest'
Forrest live webapp (Jetty) ........ Launch 'forrest run'
.................................... Launch servlet WAR
.................................... Plugins (general issues)
.................................... Plugin: IMSManifest
.................................... Plugin: OpenOffice.org
.................................... Plugin: Simplified Docbook
Forrest skins ...................... Skins (general issues)
.................................... Tools (general issues)
.................................... Tool: Eclipse config
.................................... Tool: XXE config
XML grammars & validation .......... XML grammars & validation
--------------------------


Mime
View raw message