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: [PROPOSAL] db changes on release branches banned
Date Thu, 18 Sep 2014 16:09:41 GMT
I agree with Daan and Wido. It would make testing much easier.

On Thu, Sep 18, 2014 at 8:30 AM, Wido den Hollander <wido@widodh.nl> wrote:

>
>
> On 09/18/2014 04:18 PM, Daan Hoogland wrote:
> > H,
> >
> > I would like to propose that any db change on a branch scheduled for
> > release be banned. During the 4.4.0 cycle most merge conflicts occured in
> > db related (sql) files. Also I heard several times of people having
> > problems with testing that led to them having to wipe the db and
> > re-init'ing it. This discipline is a workaround for commit based upgrades
> > and helps us while we have this not in place.
> >
>
> +1 for me on that. It has frustrated me a couple of times where the DB
> changes during tests on a release branch.
>
> Like you mention, imho it would be best if we had a database version
> numbering which is decoupled from the releases, but while that's not
> there, let's not do any DB changes to release branches. It makes testing
> a lot easier.
>
> Wido
>



-- 
*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