Hi,
I'm usually placing those types of notes in the General Upgrade Notes
(upgrade/upgrade_notes.rst), Is it make more sense to have that in the
fixed_issue? Although the 4.5 fixed_issue file is impressively large so
people might not go at the bottom of the page...
BTW thanks, that's great :-) !
Thanks!
I think it’s OK to have it in master as well. We can remove it when most people
that currently use 4.3 are upgraded to either 4.4 or newer.
Regards,
Remi
On 12 Mar 2015, at 11:45, Rohit Yadav wrote:
> Hi Remi,
>
> I've merged the PRs on 4.4/4.5 and master branches. Do you want me to
Hi Remi,
I've merged the PRs on 4.4/4.5 and master branches. Do you want me to
revert the commits on master then?
On Thursday 12 March 2015 03:53 PM, Remi Bergsma wrote:
Hi Sebastien,
Thanks for the pointer, I’ve send pull requests to add it to 4.4 and 4.5. Not sure
if we want to add it to ma
Hi Sebastien,
Thanks for the pointer, I’ve send pull requests to add it to 4.4 and 4.5. Not
sure if we want to add it to master as well? Could make sense if people will
upgrade from 4.3 -> 4.6 in the future. Let me know!
If there was an easier way to add it to multiple branches at once I’m happ
On Mar 11, 2015, at 5:26 PM, Remi Bergsma wrote:
> Hi,
>
> It might be worth noting in the release notes of ACS 4.5 that CLOUDSTACK-7595
> is resolved, as this changes behaviour. We ran into this in 4.4 already where
> we suddenly had timeouts that were not there before and it’s not immediate
