geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1883) Make sure all documentation is clearly marked as G 1.0 or G 1.1
Date Tue, 25 Apr 2006 14:16:07 GMT
    [ ] 

Aaron Mulder commented on GERONIMO-1883:

First of all, I think the plan for 1.1 is a mistake.  Since every deployment plan must change,
I think we should copy every 1.0 page and make a 1.1 version of it with the correct information
(alternately, update them all in place and switch the header from saying 1.0 to saying 1.1
as you do it).  If someone is looking for help on how to deploy a web app, it's no good to
have a page full of incorrect syntax and another page somewhere else saying "everywhere you
see a configId you should change it like this..."

Regardless of that, I still feel strongly that every 1.0 page should be clearly marked 1.0.
 We have to expect that someone looking for information on, say, web apps or EJBs in Geronimo
will find their way to the 1.0 documentation page, follow the instructions, and then ask why
it doesn't work.  Thanks.

> Make sure all documentation is clearly marked as G 1.0 or G 1.1
> ---------------------------------------------------------------
>          Key: GERONIMO-1883
>          URL:
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: documentation
>     Versions: 1.0
>     Reporter: Aaron Mulder
>     Assignee: Hernan Cunico
>     Priority: Critical
>      Fix For: 1.1

> As we roll out 1.1, with different deployment plan syntax, it'll be extremely import
that *all* documentation clearly states (e.g. in big bold text at the top) which Geronimo
version it applies to.  We can go ahead and mark all the 1.0 content as 1.0 now, and just
update the marker as the content itself is updated to 1.1.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message