Thanks Simon. :) *Will STEVENS* Lead Developer
*CloudOps* *| *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ On Wed, Mar 2, 2016 at 4:14 PM, Simon Weller <swel...@ena.com> wrote: > Will, > > You have our support! > > Let us know what we can do to help. > > - Si > > ________________________________________ > From: Paul Angus <paul.an...@shapeblue.com> > Sent: Wednesday, March 2, 2016 3:09 PM > To: dev@cloudstack.apache.org > Subject: Re: 4.9 Release Management > > That's good enough for me (tm). you're figuring out what you need to > figure out. I know the feeling. :) > > We probably need to have a concensus around release cadence and stick to > it for a while. Otherwise we're going to lose some credibility as project. > > > > > > From: Will Stevens <wstev...@cloudops.com> > Sent: 2 Mar 2016 20:46 > To: dev@cloudstack.apache.org > Subject: Re: 4.9 Release Management > > I don't think I can answer that at this time. My personal opinion is that > CI is more important than the release timeline, but others may not share > this opinion (as it is only my opinion). I am full steam ahead trying to > review what we have in place and the work that different parties have done > on CI to date. I am hoping to have a CI implementation setup in my > environment soon, which will enable me to better assess the current state > of affairs. > > There are a lot of moving parts involved and I will be the first to admit > that I don't have a firm grasp on everything yet, so reviewing our Marvin > test coverage and output is something I have not yet had a chance to > tackle. > > Does that answer your question well enough? :) > > *Will STEVENS* > Lead Developer > > *CloudOps* *| *Cloud Solutions Experts > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 > w cloudops.com *|* tw @CloudOps_ > > On Wed, Mar 2, 2016 at 12:25 PM, Paul Angus <paul.an...@shapeblue.com> > wrote: > > > Thanks for taking up the baton Will et al. > > > > Just for clarity - given that getting CI 'done' will take some time > > (mainly because of the state of the Marvin Tests and Marvin output) - are > > 'we' now dropping the monthly releases? > > > > > > [image: ShapeBlue] <http://www.shapeblue.com> > > Paul Angus > > VP Technology , ShapeBlue > > d: *+44 203 617 0528 | s: +44 203 603 0540* > > <+44%20203%20617%200528%20%7C%20s:%20+44%20203%20603%200540> | m: > > *+44 7711 418784* <+44%207711%20418784> > > e: *paul.an...@shapeblue.com | t: @cloudyangus* > > <paul.an...@shapeblue.com%20%7C%20t:%20@cloudyangus> | w: > > *www.shapeblue.com* <http://www.shapeblue.com> > > a: 53 Chandos Place, Covent Garden London WC2N 4HS UK > > Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue > > Services India LLP is a company incorporated in India and is operated > under > > license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a > > company incorporated in Brasil and is operated under license from Shape > > Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of > > South Africa and is traded under license from Shape Blue Ltd. ShapeBlue > is > > a registered trademark. > > This email and any attachments to it may be confidential and are intended > > solely for the use of the individual to whom it is addressed. Any views > or > > opinions expressed are solely those of the author and do not necessarily > > represent those of Shape Blue Ltd or related companies. If you are not > the > > intended recipient of this email, you must neither take any action based > > upon its contents, nor copy or show it to anyone. Please contact the > sender > > if you believe you have received this email in error. > > > > > > > > > Paul Angus > VP Technology , ShapeBlue > > > t: @cloudyangus<tel:@cloudyangus> > > e: paul.an...@shapeblue.com<mailto:paul.an...@shapeblue.com> > | w: www.shapeblue.com<http://www.shapeblue.com> > > > > > > -----Original Message----- > > From: Will Stevens [mailto:williamstev...@gmail.com] > > Sent: 02 March 2016 17:15 > > To: dev@cloudstack.apache.org > > Subject: 4.9 Release Management > > > > Hello Everyone, > > I have mentioned this in other related threads, but I wanted to make an > > official thread on the topic. > > > > I am nominating myself as the release manager for 4.9. Please feel free > to > > discuss if you have comments or concerns. > > > > I will not be working alone, I will be assisted by Koushik Das and > Patrick > > Dube. I will be running point, but all three of us will be working > together > > as a unit for this release. > > > > Our main focus for this release is the integration of hardware Continuous > > Integration (CI) into the PR flow. Koushik and his team will be setting > up > > a CI environment which will be used for testing PRs and I will also be > > setting up a CI environment for testing PRs. > > > > The details of the CI integration will be handled publicly, but we will > > likely have to work with a minimum viable implementation initially and > move > > forward from there. Here are some of the key aspects of the CI which are > > top of mind for me. > > > > - Standardize a feedback mechanism to post the result of CI runs back to > > the relevant PR. I believe the best way to do this would be to post a > > summary of the CI run in the PR thread on Github. With the existing > > integration, this will then get pushed to the mailing list (since all > > comments on a PR are pushed to the mailing list). > > - Ideally, we will also make the CI logs available for the run. We are > > still working out the details of how we do this, but we will likely be > > pushing the logs to an object store with a cleanup window to remove the > > logs after a set period of time (probably a week). This should give > people > > the opportunity to pull the logs if they are interested in the test > > results, but will reduce the need for ever growing storage. > > - In order to parallelize the CI operations, we will not be automatically > > kicking off a CI run for every PR for now. Instead, we will communicate > > between us and each run distinct PRs so we can maximize the utilization > of > > our hardware. > > > > Some longer term goals of the CI in my mind are as follows: > > > > - I would like the core CI framework to be easily distributed and > > accessible to anyone who has hardware available. This would enable anyone > > to setup a CI on their hardware and it would automatically be hooked up > to > > feedback the results to the Github PRs. I feel this is very important > long > > term because every individual or organization depends on a different > > configuration and hardware setup, so it empowers them to validate their > own > > use case while adding value back to the community. > > > > Additional details will follow, namely the release schedule etc. > > > > Please contribute your ideas and feedback. > > > > Cheers, > > > > Will > > Find out more about ShapeBlue and our range of CloudStack related > services: > > IaaS Cloud Design & Build > > <http://shapeblue.com/iaas-cloud-design-and-build//> | CSForge – rapid > > IaaS deployment framework <http://shapeblue.com/csforge/> > > CloudStack Consulting <http://shapeblue.com/cloudstack-consultancy/> | > CloudStack > > Software Engineering > > <http://shapeblue.com/cloudstack-software-engineering/> > > CloudStack Infrastructure Support > > <http://shapeblue.com/cloudstack-infrastructure-support/> | CloudStack > > Bootcamp Training Courses <http://shapeblue.com/cloudstack-training/> > > > Find out more about ShapeBlue and our range of CloudStack related services: > IaaS Cloud Design & Build< > http://shapeblue.com/iaas-cloud-design-and-build//> | CSForge – rapid > IaaS deployment framework<http://shapeblue.com/csforge/> > CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/> | > CloudStack Software Engineering< > http://shapeblue.com/cloudstack-software-engineering/> > CloudStack Infrastructure Support< > http://shapeblue.com/cloudstack-infrastructure-support/> | CloudStack > Bootcamp Training Courses<http://shapeblue.com/cloudstack-training/> >
