cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Abhinandan Prateek <abhinandan.prat...@shapeblue.com>
Subject Re: 4.9 Release Management
Date Wed, 09 Mar 2016 05:29:06 GMT

[ShapeBlue]<http://www.shapeblue.com>
Abhinandan Prateek
Software Architect      ,       ShapeBlue


d:       | s: +44 203 603 0540<tel:|%20s:%20+44%20203%20603%200540>      |      m: 
    +91 970 11 99011<tel:+91%20970%2011%2099011>

e:      abhinandan.prateek@shapeblue.com | t: <mailto:abhinandan.prateek@shapeblue.com%20|%20t:>
        |      w:      www.shapeblue.com<http://www.shapeblue.com>

a:      53 Chandos Place, Covent Garden London WC2N 4HS UK


[cid:image0d9449.png@84acf60b.4ab55f1a]


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.




On 03/03/16, 9:20 AM, "Koushik Das" <koushik.das@accelerite.com> wrote:


>Thanks Will for initiating the discussion on 4.9 release management. As already mentioned,
I along with Patrick will be helping out Will with the release process.
>
>Having a reliable CI system is very important going forward. There are discussions already
happening in the list related to it. I agree that CI should be the top priority for 4.9 release.
>
>The initial idea is to run the CI manually against each PR and publish the results in
github itself. The details of the CI environment, test scenarios and configurations will be
published as well. Simulator based tests are already running as part of Travis, if required
some more tests scenarios can be added there.

Good to see you taking up CI implementation for cloudstack with others. Do you yet have timeline
to publish a roadmap or a plan for this effort ?

>
>In the longer run, if more contributors/organizations come up with their own CI environment
and help test PRs then it will be even better.
>
>-Koushik
>________________________________________
>From: Will Stevens <williamstevens@gmail.com>
>Sent: Wednesday, March 2, 2016 10:44 PM
>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
>
>
>DISCLAIMER
>==========
>This e-mail may contain privileged and confidential information which is the property
of Accelerite, a Persistent Systems business. It is intended only for the use of the individual
or entity to which it is addressed. If you are not the intended recipient, you are not authorized
to read, retain, copy, print, distribute or use this message. If you have received this communication
in error, please notify the sender and delete all copies of this message. Accelerite, a Persistent
Systems business does not accept any liability for virus infected mails.
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/>

Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message