Re: [DISCUSS] upgrade to 4.11

2017-07-11 Thread Daan Hoogland
of which the heart is full, the mouth spilled ... (free from ancient dutch saying ;) On Tue, Jul 11, 2017 at 3:56 PM, Will Stevens wrote: > Oh ok. DB upgrade, not a new skeleton for the upgrade path between version > (hypervisors, etc...). > > My bad. :) > > *Will Stevens* > CTO > >

Re: [DISCUSS] upgrade to 4.11

2017-07-11 Thread Will Stevens
Oh ok. DB upgrade, not a new skeleton for the upgrade path between version (hypervisors, etc...). My bad. :) *Will Stevens* CTO On Tue, Jul 11, 2017 at 9:41 AM, Daan Hoogland wrote: > No I am creating the upgrade code for the next version. > (schema-41000to41100 and

Re: [DISCUSS] upgrade to 4.11

2017-07-11 Thread Daan Hoogland
No I am creating the upgrade code for the next version. (schema-41000to41100 and upgrade java class) On 11/07/17 15:29, "williamstev...@gmail.com on behalf of Will Stevens" wrote: Not sure I have an answer for that. Are you creating a PR to this set of documentation or where are you w

Re: [DISCUSS] upgrade to 4.11

2017-07-11 Thread Will Stevens
Not sure I have an answer for that. Are you creating a PR to this set of documentation or where are you working? https://github.com/apache/cloudstack-docs-rn/tree/master/source/upgrade *Will Stevens* CTO On Tue, Jul 11, 2017 at 9:15 AM, Daan Hoogland wrote: > Devs, > >

[DISCUSS] upgrade to 4.11

2017-07-11 Thread Daan Hoogland
Devs, I am busy creating the skeleton upgrade code for our next version (working name 4.11). Are we still supporting all direct upgrades from 2.x onward or should we only assume upgrade paths from 4.y onwards? Tnx, daan.hoogl...@shapeblue.com  www.shapeblue.com 53 Chandos Place, Covent Garden,