I think part of the trouble with using a link to jira, though it's definitely a good start, is that the bugs morph over time ... i.e., as we begin to fix bugs in the trunk, the bugs in that query will change state.
It seems better to me to take a snapshot and post it somewhere. -----Original Message----- From: Richard Feit Sent: Wednesday, November 10, 2004 8:14 AM To: Beehive Developers Subject: Re: [BUG TRIAGE] [Fwd: [jira] Created: (BEEHIVE-72) Webapp build warning] Definitely. How about this link? http://nagoya.apache.org/jira/secure/IssueNavigator.jspa?pid=10570&types =1&resolutionIds=-1&refreshFilter=false&reset=update&summary=true&descri ption=true&hide=%3C%3C+View+%26+Hide I'm still getting the hang of making bookmarkable URLs for JIRA queries, but I think that one should give a list of all unresolved bugs in Beehive. [EMAIL PROTECTED] wrote: >>We probably should get into the habit of having a known issues doc for >>every release... >> >> > >Perhaps just a link into JIRA? I don't think we can get a list of >issues-still-open-as-of-verson-XX, but it'd be a start. > >http://nagoya.apache.org/jira/secure/IssueNavigator.jspa?start=0&tempMa x=1000&view=&decorator=printable&mode=hide > > -bob > > >
