no, though that's debatable: one fix is that adding the same public key to a domain under a different name no longer works. It is a fix for retrieving keys consistently. retrieving the second name would return the key with the first name. Now it can not be entered twice anymore it will always return the same public key / name pair.
Not sure if this is worth mentioning in the rn, but it is to reporter so why not. On Thu, Jun 25, 2015 at 8:08 AM, Erik Weber <terbol...@gmail.com> wrote: > Gotcha, should add that. > > Are there any API changes that you know of in 4.4.4? > > -- > Erik > > On Thu, Jun 25, 2015 at 8:06 AM, Daan Hoogland <daan.hoogl...@gmail.com> > wrote: > >> I'll have a look, For the upgrade instructions 4.4.3 should work best. >> >> The only gotcha for people from 4.4.3 that I know of is a setting >> "router.reboot.when.outofband.migrated". hte default 'false' gives old >> behavior. 'true' gives the 4.4.3 behavior. >> >> >> On Thu, Jun 25, 2015 at 12:20 AM, Erik Weber <terbol...@gmail.com> wrote: >> > initial version at https://github.com/apache/cloudstack-docs-rn/pull/23 >> > >> > it's getting late here, if anyone want's to pick it up feel free to fork >> > and continue. >> > >> > -- >> > Erik >> > >> > On Wed, Jun 24, 2015 at 11:33 PM, Erik Weber <terbol...@gmail.com> >> wrote: >> > >> >> in the perfect world I guess we would all be laying on a beach somewhere >> >> sunny >> >> >> >> i'll bring these `issues` to another thread for discussion >> >> >> >> any upgrade instructions for 4.4.4, or is it ok to stay with the upgrade >> >> from 4.4.1 instructions? >> >> >> >> -- >> >> Erik >> >> >> >> On Wed, Jun 24, 2015 at 11:18 PM, Daan Hoogland < >> daan.hoogl...@gmail.com> >> >> wrote: >> >> >> >>> 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 >> >>> >> >> >> >> >> >> >> >> -- >> Daan >> -- Daan
