[GitHub] [cloudstack-documentation] weizhouapache commented on pull request #300: Guest OS and hypervisor mappings
weizhouapache commented on PR #300: URL: https://github.com/apache/cloudstack-documentation/pull/300#issuecomment-1373541033 @blueorangutan docbuild -- 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-documentation] blueorangutan commented on pull request #300: Guest OS and hypervisor mappings
blueorangutan commented on PR #300: URL: https://github.com/apache/cloudstack-documentation/pull/300#issuecomment-1373541645 @weizhouapache a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress. -- 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-documentation] blueorangutan commented on pull request #300: Guest OS and hypervisor mappings
blueorangutan commented on PR #300: URL: https://github.com/apache/cloudstack-documentation/pull/300#issuecomment-1373542193 QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/300. (QA-JID 25) -- 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: [4.18][RELEASE] timeline
Thanks, Daan, looking good. --- Nux www.nux.ro On 2023-01-03 09:39, Daan Hoogland wrote: Happy new year to all, I wish you enjoyment wisdom health and strength in your work and your private lives. I wish to inform you of my plans for the coming weeks as a Release Manager: At the moment we have - 32 issues and - 31 pull requests marked for 4.18. These numbers were a bit lower end of last year and to prevent shooting at a moving target I want to share the following. This week, I want to create a milestone 4.18.1.0 and move any issue that - reads as a bug report - does not have someone assigned - does not have a linked pull request In addition I want to move to milestone 4.19.0.0, any issue that - reads as an enhancement or a feature request - does not have a pull request linked In two weeks, on the 17th, I want to call a freeze on merges to main for stabilization. At the end of January, approximately on the 31st I want to release RC1. I am open to any request for change in this schedule. There are some hefty PRs out that I imagine everybody wants in, and you may have quick and handy or vital fixes to add as well. Please feel free to address me on this thread or on any DM I appear responsive on. regards,
Re: [4.18][RELEASE] timeline
Thanks Daan - LGTM. Regards. From: Nux Sent: Friday, January 6, 2023 21:49 To: dev@cloudstack.apache.org Cc: users Subject: Re: [4.18][RELEASE] timeline Thanks, Daan, looking good. --- Nux www.nux.ro On 2023-01-03 09:39, Daan Hoogland wrote: > Happy new year to all, I wish you enjoyment wisdom health and strength > in > your work and your private lives. > > I wish to inform you of my plans for the coming weeks as a Release > Manager: > At the moment we have > - 32 issues and > - 31 pull requests > marked for 4.18. These numbers were a bit lower end of last year and to > prevent shooting at a moving target I want to share the following. > > This week, I want to create a milestone 4.18.1.0 and move any issue > that > - reads as a bug report > - does not have someone assigned > - does not have a linked pull request > In addition I want to move to milestone 4.19.0.0, any issue that > - reads as an enhancement or a feature request > - does not have a pull request linked > > In two weeks, on the 17th, I want to call a freeze on merges to main > for > stabilization. > At the end of January, approximately on the 31st I want to release RC1. > > I am open to any request for change in this schedule. There are some > hefty > PRs out that I imagine everybody wants in, and you may have quick and > handy > or vital fixes to add as well. Please feel free to address me on this > thread or on any DM I appear responsive on. > > regards,
