[DISCUSS] release and release manager 4.18
Hello everybody, As Abhishek is wrapping up the 4.17.1 release. I´d like to start the discussion about 4.18. Nobody has volunteered as the next release manager yet and I'd like to give the community the opportunity to prevent it becoming me. My idea is that we will have set a feature freeze date and then a target date for the first RC. Iḿ not proposing one now as mine would probably be too tight a deadline for new features and there are some big ones out there that we'd want in. Please let us all know what you have in the pipeline and what you want in and what time you need, so we can discuss if it is feasible for 4.18. Also please come forward if you want this task of triaging issues and PRs and tagging them to go in the release. thanks -- Daan
Re: [DISCUSS] release and release manager 4.18
+1 thanks for volunteering as 4.18 RM Daan. Regards. Regards. From: Daan Hoogland Sent: Tuesday, September 20, 2022 7:53:53 PM To: dev ; users Subject: [DISCUSS] release and release manager 4.18 Hello everybody, As Abhishek is wrapping up the 4.17.1 release. I´d like to start the discussion about 4.18. Nobody has volunteered as the next release manager yet and I'd like to give the community the opportunity to prevent it becoming me. My idea is that we will have set a feature freeze date and then a target date for the first RC. Iḿ not proposing one now as mine would probably be too tight a deadline for new features and there are some big ones out there that we'd want in. Please let us all know what you have in the pipeline and what you want in and what time you need, so we can discuss if it is feasible for 4.18. Also please come forward if you want this task of triaging issues and PRs and tagging them to go in the release. thanks -- Daan
Re: [DISCUSS] release and release manager 4.18
+1 to Daan :-) From: Rohit Yadav Sent: Tuesday, September 20, 2022 9:43 AM To: us...@cloudstack.apache.org ; dev Subject: Re: [DISCUSS] release and release manager 4.18 EXTERNAL EMAIL: This message originated outside of ENA. Use caution when clicking links, opening attachments, or complying with requests. Click the "Phish Alert Report" button above the email, or contact MIS, regarding any suspicious message. +1 thanks for volunteering as 4.18 RM Daan. Regards. Regards. From: Daan Hoogland Sent: Tuesday, September 20, 2022 7:53:53 PM To: dev ; users Subject: [DISCUSS] release and release manager 4.18 Hello everybody, As Abhishek is wrapping up the 4.17.1 release. I´d like to start the discussion about 4.18. Nobody has volunteered as the next release manager yet and I'd like to give the community the opportunity to prevent it becoming me. My idea is that we will have set a feature freeze date and then a target date for the first RC. Iḿ not proposing one now as mine would probably be too tight a deadline for new features and there are some big ones out there that we'd want in. Please let us all know what you have in the pipeline and what you want in and what time you need, so we can discuss if it is feasible for 4.18. Also please come forward if you want this task of triaging issues and PRs and tagging them to go in the release. thanks -- Daan
[GitHub] [cloudstack-go] mlsorensen commented on pull request #41: FindHostsForMigration returns a list response
mlsorensen commented on PR #41: URL: https://github.com/apache/cloudstack-go/pull/41#issuecomment-1252681221 @davidjumani I found the issue - I didn't have `goimports` installed. I changed the makefile slightly because I couldn't figure out how to get the `mockgen` dependency properly set up as temp in the repo, so this allows me to set it to use `mockgen` from my `~/go/bin`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [cloudstack-go] mlsorensen opened a new pull request, #42: Add explicit POST functions
mlsorensen opened a new pull request, #42: URL: https://github.com/apache/cloudstack-go/pull/42 Eventually CloudStack could advertise which APIs prefer POST (set via annotations on the API classes), this will make that easier to integrate by pushing the selection of which method to use into the code gen. Right now this PR still decides POST based off of a few API command names, but it does so in code gen rather than in the generated client. Also allows to select POST for custom APIs, in the even that a user needs to manually build a POST call. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [DISCUSS] release and release manager 4.18
Sorry to interrupt. I'm curious to know how is the release procedure. Is it possible for me to help or should I be a PMC member? --- Original Message --- On Tuesday, September 20th, 2022 at 4:52 PM, Simon Weller wrote: > > > +1 to Daan :-) > > From: Rohit Yadav rohit.ya...@shapeblue.com > > Sent: Tuesday, September 20, 2022 9:43 AM > To: us...@cloudstack.apache.org us...@cloudstack.apache.org; dev > dev@cloudstack.apache.org > > Subject: Re: [DISCUSS] release and release manager 4.18 > > EXTERNAL EMAIL: This message originated outside of ENA. Use caution when > clicking links, opening attachments, or complying with requests. Click the > "Phish Alert Report" button above the email, or contact MIS, regarding any > suspicious message. > > > > +1 thanks for volunteering as 4.18 RM Daan. > > Regards. > > Regards. > > From: Daan Hoogland daan.hoogl...@gmail.com > > Sent: Tuesday, September 20, 2022 7:53:53 PM > To: dev dev@cloudstack.apache.org; users us...@cloudstack.apache.org > > Subject: [DISCUSS] release and release manager 4.18 > > Hello everybody, > As Abhishek is wrapping up the 4.17.1 release. I´d like to start the > discussion about 4.18. Nobody has volunteered as the next release manager > yet and I'd like to give the community the opportunity to prevent it > becoming me. My idea is that we will have set a feature freeze date and > then a target date for the first RC. Iḿ not proposing one now as mine would > probably be too tight a deadline for new features and there are some big > ones out there that we'd want in. > Please let us all know what you have in the pipeline and what you want in > and what time you need, so we can discuss if it is feasible for 4.18. > Also please come forward if you want this task of triaging issues and PRs > and tagging them to go in the release. > thanks > > -- > Daan > signature.asc Description: OpenPGP digital signature
