I'm for option 1. I don't want to keep documentation issues separate from code issues.
Am 01.10.2010 um 18:58 schrieb Howard Lewis Ship <[email protected]>: > With the move to Confluence, documentation is no longer linked to the > release cycle. I still like the idea of using JIRA to track problems > and improvements to the documentation, but it seems odd to list those > changes in the release notes. > > Either we should close such issues with no release number OR we should > create a seperate JIRA category (i.e., "TAPDOC") to track > documentation issues. > > Thoughts? > > -- > Howard M. Lewis Ship > > Creator of Apache Tapestry > > The source for Tapestry training, mentoring and support. Contact me to > learn how I can get you up and productive in Tapestry fast! > > (971) 678-5210 > http://howardlewisship.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
