cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Tutkowski <mike.tutkow...@solidfire.com>
Subject Re: [BLOCKER] Master broken due to PR 714 (CLOUDSTACK-8750)
Date Wed, 02 Sep 2015 01:01:42 GMT
At several of the companies where I've worked before, we would hold "bug
court" a couple times per week as the release marched on.

Representatives from different areas (product marketing, sales, support,
engineering, etc.) would attend and we'd go through all issues opened since
the previous bug court and prioritize them. Depending on how close we were
to GA for a release, less critical defects (unless trivial to fix) would be
postponed until a subsequent release.

This allowed us to control more closely what went into a release the closer
we got to GA, but it's probably not practical for CloudStack as it requires
a fair amount of discussion for each new issue.

On Tue, Sep 1, 2015 at 2:11 AM, Daan Hoogland <daan.hoogland@gmail.com>
wrote:

> There is something like this on the page by Remi on the new release
> procedure. It is one of the lesser things about it. I think we should only
> look at stability. The discussion on what is minor or major is not
> something we want to need to have.
>
> On Tue, Sep 1, 2015 at 3:48 AM, Mike Tutkowski <
> mike.tutkowski@solidfire.com
> > wrote:
>
> > What do we think, though, about tickets listed as Minor going in at this
> > point in 4.6 development?
> >
> > If they entail a trivial change in only a file or two, it's probably OK,
> > but where should we draw the line?
> >
> > At some point as the release goes on, we should stop accepting PRs that
> are
> > tied to Minor tickets and only allow churn in that branch for more major
> > issues. Those PRs tied to Minor tickets can then be for the next release.
> >
> > Thoughts?
> >
> > On Mon, Aug 31, 2015 at 12:03 PM, Daan Hoogland <daan.hoogland@gmail.com
> >
> > wrote:
> >
> > > As David says; Though I think it is very polite of you to wait and ask
> > > around, you have this right if you can show master doesn't work.
> > >
> > > On Mon, Aug 31, 2015 at 6:06 PM, David Nalley <david@gnsa.us> wrote:
> > >
> > > > On Mon, Aug 31, 2015 at 12:57 AM, Koushik Das <
> koushik.das@citrix.com>
> > > > wrote:
> > > > > I am no longer able to start MS after this. I did a clean build
> > > followed
> > > > by starting MS. Did travis pass for it? Should we revert?
> > > > >
> > > >
> > > > Yes, and in general, when things break you should feel empowered to
> > > > revert (still send a note to the list, but as a committer, you have a
> > > > binding veto at your disposal - feel free to make use of it to keep
> > > > quality high.)
> > > >
> > > > --David
> > > >
> > >
> > >
> > >
> > > --
> > > Daan
> > >
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkowski@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the cloud
> > <http://solidfire.com/solution/overview/?video=play>*™*
> >
>
>
>
> --
> Daan
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
<http://solidfire.com/solution/overview/?video=play>*™*

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