Mike, Anyone can submit a PR against any branch. If they can get 2 LGTMs for it, it will be merged. After that, you could create a new 4.6 RC, and open a vote for it. While there is nothing procedurally that prevents someone from following this process, it is unlikely that the release vote would muster interest to pass.
Thanks, -John > john.burw...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London VA WC2N 4HSUK @shapeblue On Jun 16, 2016, at 2:29 AM, Tutkowski, Mike <mike.tutkow...@netapp.com> wrote: > > OK - I can always deliver the plug-in for 4.6 directly to my customers and > first check it into the CloudStack repo maybe in 4.10 or later. > >> On Jun 16, 2016, at 12:21 AM, Rajani Karuturi <raj...@apache.org> wrote: >> >> "We will only fix bugs in this release branch, no back porting of new >> features" - >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+principles+for+Apache+CloudStack+4.6+and+up >> >> I would prefer a PR on master for 4.9+ >> >> >> >> ~Rajani >> >> On Thu, Jun 16, 2016 at 7:12 AM, Tutkowski, Mike <mike.tutkow...@netapp.com> >> wrote: >> >>> Hi, >>> >>> >>> This is mainly a release-management question, but - of course - anyone who >>> knows, please feel free to comment. >>> >>> >>> I have been developing a new API plug-in for a customer. The customer is >>> using CloudStack 4.6. >>> >>> >>> I'd like to contribute the plug-in to our official repo, but I'm wondering >>> if I can open a PR as far back as 4.6 (and, of course, I'd like to have >>> this plug-in in all subsequent releases, as well). >>> >>> >>> Thoughts on this? >>> >>> >>> Thanks! >>> >>> Mike >>>
