yes, you are right, but in a perfect world we wouldn't have any issues ;) I'd say mark them as 'assorted improvements on xxx-yyy'
On Wed, Jun 24, 2015 at 11:15 PM, Erik Weber <terbol...@gmail.com> wrote: > i'm working my way through the git commits that reference jira issues to > mark them as fixed in 4.4.4 > it isn't always straight forward though, as sometimes commits are > improvements to existing issues that has already been released. > > take CLOUDSTACK-6181 for instance, it was released with 4.4.0, but has > commits in 4.4.4 that improves it. > in a perfect world I guess those commits really should have been separate > issues > > -- > Erik > > > > On Wed, Jun 24, 2015 at 10:58 PM, Daan Hoogland <daan.hoogl...@gmail.com> > wrote: > >> btw CLOUDSTACK-8545 is marked fixed in 4.4.4 as well >> >> On Wed, Jun 24, 2015 at 10:53 PM, Daan Hoogland <daan.hoogl...@gmail.com> >> wrote: >> > there is the git log >> > >> > On Wed, Jun 24, 2015 at 10:51 PM, Erik Weber <terbol...@gmail.com> >> wrote: >> >> There's only one issue (CLOUDSTACK-8537) with fix version 4.4.4 marked >> as >> >> resolved in Jira. >> >> >> >> I'm guessing that's wrong, so who know what's been fixed? >> >> >> >> -- >> >> Erik >> >> >> >> On Wed, Jun 24, 2015 at 10:38 PM, Daan Hoogland < >> daan.hoogl...@gmail.com> >> >> wrote: >> >> >> >>> Someone feeling the urge to write release notes for 4.4.4? Looking for >> >>> a volunteer. >> >>> >> >>> -- >> >>> Daan >> >>> >> > >> > >> > >> > -- >> > Daan >> >> >> >> -- >> Daan >> -- Daan
