On Sep 12, 2014, at 6:52 AM, Daan Hoogland <daan.hoogl...@gmail.com> wrote:
> Sebastien, a generated file is more reliable, isn't it? or else one of my > former manageres favorite Stalin quote: "Trust is good, control is better" > yes and I even wrote the script that pulls the bugs form jira: https://git-wip-us.apache.org/repos/asf?p=cloudstack-docs-rn.git;a=blob;f=utils/jira.py;h=c4b931de0aade4416f465858a7fea50ab7be01f8;hb=master But it would be nice if committers would get in the habit of updating the CHANGES files when they fix a bug. Otherwise why do we have a CHANGES file in the first place ? > > On Fri, Sep 12, 2014 at 12:33 PM, Sebastien Goasguen <run...@gmail.com> > wrote: > >> >> On Sep 11, 2014, at 10:15 PM, Pierre-Luc Dion <pd...@cloudops.com> wrote: >> >>> Hi Daan, >>> >>> could you create following public Jira filter to start Release-Notes for >>> 4.3.1 and 4.4.1. >>> >>> 4.4.1 fixed >>> project = CLOUDSTACK AND type = Bug AND fixVersion = 4.4.1 AND resolution >>> != "\"Unresolved\"" ORDER BY created DESC, priority DESC, key ASC >>> >>> 4.4.1 known >>> project = CLOUDSTACK AND type = Bug AND (affectedVersion = 4.4.1 or >>> affectedVersion = 4.4.0) AND resolution is EMPTY AND level = "Public" >> ORDER >>> BY priority DESC, key ASC >>> >>> 4.3.1 fixed >>> project = CLOUDSTACK AND type = Bug AND fixVersion = 4.3.1 AND resolution >>> != "\"Unresolved\"" ORDER BY created DESC, priority DESC, key ASC >>> >> >> I have tried to keep the CHANGES.md file in the 4.3 branch up to date, so >> it should contain the list of bug fixed in 4.3.1 >> >>> 4.3.1 known >>> project = CLOUDSTACK AND type = Bug AND (affectedVersion = 4.3.1 or >>> affectedVersion = 4.3.0) AND resolution is EMPTY AND level = "Public" >> ORDER >>> BY priority DESC, key ASC >>> >>> >>> Also , does anyone is working on RN of 4.4.1 or 4.3.1? I can work on >> 4.4.1, >>> maybe on the 4.3.1. >> >> > > > -- > Daan
