On Fri, Jul 19, 2013 at 09:09:26AM -0400, Chip Childers wrote: > Hi all, > > I've been working on the release notes for 4.1.1, and when I got to the > known issues section I took a look at past releases. > > For the 4.0.x series, we used a query that checked for unresolved bugs > that had a fix version of the release that the notes were for. This > doesn't seem quite right, since in reality, the know errors are all open > bugs that aren't limited to *future* releases. > > While it's unfortunate to have such a long list, isn't a query like: > > project = CLOUDSTACK AND resolution = Unresolved and type = Bug AND > affectedVersion != '4.2.0' ORDER BY priority DESC > > really the best query to represent the know issues with 4.1.1? And > actually, there is a problem with that query. Since affectedVersion is > actually a list field, I'm still trying to figure out how to exclude > only the bugs that are ONLY affecting 4.2.0. > > Thoughts?
Joe and I discussed this on IRC. Here's the query that we're suggesting: project = CLOUDSTACK AND resolution = Unresolved AND type = Bug AND affectedVersion in releasedVersions() ORDER BY priority DESC I'll use that for 4.1.1 unless anyone objects.
