Re: [VOTE] Apache Cloudstack 4.11.0.0 LTS [RC2]

Hi All, The vote for CloudStack 4.11.0.0 *passes* with 4 PMC + 2 non-PMC votes. +1 (PMC / binding) 2 person (Mike, Daan, Wido, Rohit) +1 (non binding) 2 person (Lucian, Boris) 0 none -1 none Thanks to everyone participating. I will now prepare the release announcement to go out after 48

Re: [VOTE] Apache Cloudstack 4.11.0.0 LTS [RC2]

Copy/paste error, the vote count was: +1 (PMC / binding) 4 person (Mike, Daan, Wido, Rohit) - Rohit From: Rohit Yadav Sent: Monday, February 5, 2018 10:57:17 AM To: dev@cloudstack.apache.org Cc:

[DISCUSS] VR upgrade downtime reduction

H devs, I have recently (re-)submitted two PRs, one by Wei [1] and one by Remi [2], that reduce downtime for redundant routers and redundant VPCs respectively. (please review those) Now from customers we hear that they also want to reduce downtime for regular VRs so as we discussed this we came

change required to cloudstack.apache.org

The survey on the ACS website has stopped working (I think because the survey provider has updated their URL) Could somebody with the required karma please make a change to the file http://cloudstack.apache.org/survey.html EXISITING HTML href="//www.formwize.com/run/survey3.cfm?id=7191"

RE: change required to cloudstack.apache.org

I'm updating the website for the 4.11 release, I'll do it at the same time. paul.an...@shapeblue.com  www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue -Original Message- From: Giles Sirett [mailto:giles.sir...@shapeblue.com] Sent: 05 February 2018

Re: [VOTE] Apache Cloudstack 4.11.0.0 LTS [RC2]

+1 KMV smoketests has passed on our infra, LGTM. boris.stoya...@shapeblue.com  www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue > On 4 Feb 2018, at 11:46, Rohit Yadav wrote: > > +1 (binding) > > > Based on manual tests

Re: [VOTE] Apache Cloudstack 4.11.0.0 LTS [RC2]

Awesome! Good job everyone +1 Khosrow Moossavi Cloud Infrastructure Developer t 514.447.3456 On Mon, Feb 5, 2018 at 2:50 PM, Tutkowski, Mike wrote: > Congratulations, everyone! > > On 2/5/18, 3:09 AM, "Rohit Yadav"

Re: Releases in Progress

SEO ranking is great but putting up stuff from 3 or 4 releases in the past blows away all of the SEO benefit when someone actually goes to the page. The reader is left with the impression that the product is not actively supported (actively developed but not supported) I am not sure that SEO

Re: Releases in Progress

My point was simply that if it has good ranking already, we should update the page so we can put relevant information there so it can be easily found. Just trying to leverage it in our favor is all. *Will Stevens* Chief Technology Officer c 514.826.0190 On Mon, Feb 5,

Re: Releases in Progress

Makes sense but we should try to get rid of inaccurate stuff and stuff that makes it look like the project is not maintained. This is particularly and obviously true with pages that talk about "current" versions, roadmaps and outstanding issues. The page in question was very explicit about

Re: [VOTE] Apache Cloudstack 4.11.0.0 LTS [RC2]

Congratulations, everyone! On 2/5/18, 3:09 AM, "Rohit Yadav" wrote: Copy/paste error, the vote count was: +1 (PMC / binding) 4 person (Mike, Daan, Wido, Rohit) - Rohit

Re: Releases in Progress

Maybe we should use that wiki page for release advertising while the web page only points to it? On Tue, Feb 6, 2018 at 6:09 AM, Ron Wheeler wrote: > > Makes sense but we should try to get rid of inaccurate stuff and stuff > that makes it look like the project is

Re: Clean wiki

Ron, this page is outdated and we are still adhering somewhat to the 4.6 release principles, other then that LTS support has been added. Do you want to edit that page so they are in line? On Fri, Feb 2, 2018 at 2:00 PM, Ron Wheeler wrote: > If you search in

Re: Releases in Progress

Is there a reason we deleted it and didn't just update it? It would have been good to take advantage of the SEO that page already had working for us and just update the content to represent the latest details. No? *Will Stevens* Chief Technology Officer c 514.826.0190

Re: Releases in Progress

I read over that acronym, and " What does *SEO* stand for? Your abbreviation search returned 39 meanings ", so can you explain Steve? On Mon, Feb 5, 2018 at 10:13 PM, Will Stevens wrote: > As a project, especially around the topic of 'releases', I assume we should >

Re: Releases in Progress

Search Engine Optimization. Basically, placement of the page in google searches... *Will Stevens* Chief Technology Officer c 514.826.0190 On Mon, Feb 5, 2018 at 4:18 PM, Daan Hoogland wrote: > I read over that acronym, and " > What does *SEO*

Re: Releases in Progress

good point, thank the powers that be that i lied; i only deleted the child pages, that referred the 4.4 releases ;) https://cwiki.apache.org/confl uence/display/CLOUDSTACK/Releases+in+Progress is still there On Mon, Feb 5, 2018 at 10:19 PM, Will Stevens wrote: > Search

Re: [VOTE] Apache Cloudstack 4.11.0.0 LTS [RC2]

Also, thanks to Rohit for doing an awesome job as release manager for 4.11! On 2/5/18, 12:50 PM, "Tutkowski, Mike" wrote: Congratulations, everyone! On 2/5/18, 3:09 AM, "Rohit Yadav" wrote: Copy/paste error, the

Re: Releases in Progress

deleted On Fri, Feb 2, 2018 at 2:05 PM, Ron Wheeler wrote: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Relea > ses+in+Progress is old and needs to be update to talk about ACS 4.10, > 4.11 and 4.12. > > Ron > > -- > Ron Wheeler > President > Artifact

Re: Releases in Progress

no one had made use of it since the RM for 4.4 (no who was that again) We can undelete if you wish. I copied the only worthwhile page to the HOWTO articles. On Mon, Feb 5, 2018 at 10:02 PM, Will Stevens wrote: > Is there a reason we deleted it and didn't just update it?

Re: Releases in Progress

As a project, especially around the topic of 'releases', I assume we should leverage any SEO placement we can use. I don't have specific content I think we should put there, but if it is well placed, it would make sense that we put some detail on the page. We don't have to, but I figured I would