RE: [JBoss-dev] RE: Toward JBoss v4.0.4.GA - Part 3 - Fordevelopers

2006-04-05 Thread Dimitris Andreadis
> From: Adrian Brock
> Let's keep the process simple please.
> 
> I already:
> 1) Describe the change on the JIRA task
> 2) Update and the relevant WIKI page and link it on the JIRA task
> 3) Mark the JIRA task as requiring a doco change
> 
> I am not going to update an arbitrary number of web pages when the 
> information is already available.
> 
> If people kept their JIRA tasks to a description of the change rather 
> than using them as discussion forums, it wouldn't be as hard to 
> understand.

> Compatibility
>
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&requestI
d=12310487
> Doco
>
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&requestI
d=12310486


Thanks fine, as long as people use JIRA consistently.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


RE: [JBoss-dev] RE: Toward JBoss v4.0.4.GA - Part 3 - Fordevelopers

2006-04-05 Thread Scott M Stark
Right. Every jira issue with a documentation check box should have an
entry section in the highlights section of the release notes. Every jira
issue with a compatibility check box should have an entry in the
compatibility section.

> -Original Message-
> From: Adrian Brock 
> Sent: Wednesday, April 05, 2006 4:16 AM
> To: jboss-development@lists.sourceforge.net
> Cc: The Core
> Subject: Re: [JBoss-dev] RE: Toward JBoss v4.0.4.GA - Part 3 
> - Fordevelopers
> 
> You can already get this information from JIRA.
> 
> Let's keep the process simple please.
> 
> I already:
> 1) Describe the change on the JIRA task
> 2) Update and the relevant WIKI page and link it on the JIRA task
> 3) Mark the JIRA task as requiring a doco change
> 
> I am not going to update an arbitrary number of web pages 
> when the information is already available.
> 
> If people kept their JIRA tasks to a description of the 
> change rather than using them as discussion forums, it 
> wouldn't be as hard to understand.
> 
> e.g. You can already get this information from JIRA:
> comaptibility changes
> http://jira.jboss.com/jira/secure/IssueNavigator.jspa?view=rno
> tes&tempMax=1
> or doco changes required
> http://jira.jboss.com/jira/secure/IssueNavigator.jspa?view=rno
> tes&tempMax=1
> 
> 
> On Wed, 2006-04-05 at 05:49 -0500, Dimitris Andreadis wrote:
> > Forgot also to mention that thing that should go in the admin guide 
> > should be linked from this JIRA task:
> > 
> > http://wiki.jboss.org/wiki/Wiki.jsp?page=404UpgradeIssues
> > 
> > 
> > ---
> > This SF.Net email is sponsored by xPML, a groundbreaking scripting 
> > language that extends applications into web and mobile 
> media. Attend 
> > the live webcast and join the prime developer group 
> breaking into this new coding territory!
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
> > ___
> > JBoss-Development mailing list
> > JBoss-Development@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
> --
> 
> Adrian Brock
> Chief Scientist
> JBoss Inc.
> 
> 
> 


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development