There definitely will be a 4.11.3 release, I would expect it to be around end of Q1. We shouldn't have a problem handling a new unique entry in both with an INSERT IGNORE in the 4.12 upgrade script
Kind regards, Paul Angus paul.an...@shapeblue.com www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue -----Original Message----- From: Simon Weller <swel...@ena.com.INVALID> Sent: 03 January 2019 15:23 To: Rohit Yadav <rohit.ya...@shapeblue.com>; dev@cloudstack.apache.org Subject: Re: questions about 4.11 future Rohit, Thoughts on this? We can base it on 4.11 or the pending 4.12 master. - Si ________________________________ From: Nathan Johnson <njohn...@ena.com.INVALID> Sent: Wednesday, January 2, 2019 12:23 PM To: Rohit Yadav Cc: dev@cloudstack.apache.org Subject: questions about 4.11 future First off, is there going to be a 4.11.3 release? Assuming so, at what point would it be appropriate to add database migrations? I have a bug fix I'd like to open a PR on, but it will require a small database change - namely inserting a record into the configuration table. Is it appropriate for me to start a new migration path for 4.11.3 to facilitate this fix? Or would it be more appropriate for the release manager to do this? If you'd like, I have a 4.11.3 database migration started in my branch (i.e., added a schema-41120to41130.sql / cleanup , added a Upgrade41120to41130.java , and added the Upgrade41120to41130 class to all of the paths mentioned in DatabaseUpgradeChecker). if you'd like me to open a PR on effectively an empty 4.11.3 migrations path, and then I could make a second PR that just adds the appropriate sql statement(s) for the actual bug fix PR. Thanks in advance, Nathan Johnson
