On Wed, Oct 8, 2014 at 9:13 AM, Ivan Kelly <[email protected]> wrote: > > Flavio Junqueira writes: > > > We don't use jira only for things that need to be checked in. Infra > > tickets and podling name search are example of queues that typically > > don't check in anything. > Those are both groups which don't have any code artifact releases. We > do, and putting non code stuff in jira, means when we have a release, > jira and svn/changes.txt will be out of sync, so someone has to go in > and fix it. >
Tracking tasks in JIRA is pretty good practice. Why it is a bad idea to include them in release notes? Even you don't want to include those tickets, you could mark the ticket as specific category (e.g. documentation). Then it is easy to fill out those tickets you don't want to include in the release notes? > > > > > I was asking this just so that we could iterate, but you might as well > > just check it in and we can do it directly on the website. > Jira isn't the best tool for iterating over text. Suggestions get lost, > and quoting in comments is awkward at best. > why not use review board? we already have pretty standard tools for reviewing. > I've created a google doc if you want to give feedback: > > https://docs.google.com/document/d/1lit0QLJ58RG4-Fn0DAaTYF8naMZWzKinQL0g2VNmM3c/edit?usp=sharing > > -Ivan >
