Hi Haijiao,
We cannot accept or back port completely new features on 4.11 branch, we should
ideally only accept bugfixes but sometimes small infra/operational enhancements
do make it in minor releases.
Once 4.11.3.0 is out, we will work towards 4.13.0.0 and users can get all new
features with
I know typically 4.11.3 would not accept new features but bug fixes.
We have a couple of clients that need 'uploading local ISO via UI or API', just
wondering if 4.11.3 can include the PR Add local ISO upload via UI #3251 ,
given it's already merged into master?
Thanks !
+1 to regerate and replace the fat jar file.
Maven does allow to generate jars for the specific modules within the codebase.
That means you can edit your files and regerate the specific jar for that
module. Then you can build the client/ module so the fat jar gets the latest
code.
Regards,
Nic
Richard, I think it will be easiest to replace the jar in
/usr/share/cloudstack (by head, don't hold me to the exact path). Depending
on the distribution you run on you can edit the classpath in the startup
script, but I'd go for replacing the jar!
On Wed, Jun 5, 2019 at 7:30 PM Richard Lawley
wr
OVM ?
On Wed, Jun 5, 2019, 19:56 Rohit Yadav wrote:
> All,
>
> Bases on some conversation on a Github issue on moving to Python3 today, I
> would like to propose a PR after 4.13 is cut on deprecation of following
> hypervisors in the next major 4.14 release:
>
> - XenServer 6.2, 6.5 and older
>
All,
Bases on some conversation on a Github issue on moving to Python3 today, I
would like to propose a PR after 4.13 is cut on deprecation of following
hypervisors in the next major 4.14 release:
- XenServer 6.2, 6.5 and older
- VMware 5.x
- KVM/CentOS6/RHEL6 (though we've already voted and ag
Hi,
I'm looking to test some changes to a plugin on a production CS
deployment - my Java knowledge is a bit lacking in this area, so I'm
hoping someone can point me in the right direction. My production
servers are running from CentOS packaging - if I compile a plugin on a
development machine, is
All,
The 4.11.3.0 milestone (https://github.com/apache/cloudstack/milestone/7),
currently only has one outstanding PR.
You may go through the list of open issues and pull requests and share any
blocker or critical bug that should be fixed towards 4.11.3.0. The list of
already closed pull req
