From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Brian Avery <avery.brian@gmail.com>
Cc: toaster@yoctoproject.org
Subject: Re: RFC
Date: Fri, 6 Nov 2015 14:21:15 +0200 [thread overview]
Message-ID: <20151106122115.GB10560@linux.intel.com> (raw)
In-Reply-To: <CAKV_0eh22itpsDE=7hum=T8uyMrvaATKtR4Q3ci1rWas+L=izg@mail.gmail.com>
On Thu, Nov 05, 2015 at 01:26:49PM -0800, Brian Avery wrote:
> Hi,
>
> Maintaining migrations for toaster from the beginning of time is
> beginning to be too complex. I'd like to propose that we support
> databse migrations from the last release to the current release, only.
>
> This would still allow people to do a stepwise migration if they
> really needed to but would mean that developers would not have to
> test/stress over migrations from schema no one remembers any longer.
>
> Comments/impacts?
>
Makes sense to me. +1
--
Regards,
Ed
next prev parent reply other threads:[~2015-11-06 12:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 21:26 RFC Brian Avery
2015-11-06 9:43 ` RFC Smith, Elliot
2015-11-06 12:21 ` Ed Bartosh [this message]
2015-11-10 17:34 ` RFC Bob Cochran
2015-11-11 14:56 ` RFC Smith, Elliot
-- strict thread matches above, loose matches on Subject: below --
2004-04-01 3:54 RFC Scott@Charter
2004-04-01 4:28 ` RFC Pitichai Pitimaneeyakul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151106122115.GB10560@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=avery.brian@gmail.com \
--cc=toaster@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.