RFC

RFC

[Brian Avery]

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?

-b

Re: RFC

[Smith, Elliot]

[-- Attachment #1: Type: text/plain, Size: 806 bytes --]

On 5 November 2015 at 21:26, Brian Avery <avery.brian@gmail.com> wrote:

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

Fine by me.

Elliot


>
> Comments/impacts?
>
> -b
> --
> _______________________________________________
> toaster mailing list
> toaster@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/toaster
>



-- 
Elliot Smith
Software Engineer
Intel Open Source Technology Centre

[-- Attachment #2: Type: text/html, Size: 1715 bytes --]

Re: RFC

[Ed Bartosh]

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

Re: RFC

[Bob Cochran]

On 11/05/2015 04:26 PM, 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?


I'm all for it, but can you please upgrade toaster to work with Django 
1.8.6 at the same time?

As you probably know, migrations are now integrated into Django and no 
longer require South.  I work with Django on a regular basis, and I seem 
to have less migration headaches these days, although I know part of my 
improved quality of life was getting away from MySQL and moving to 
postgresql.

Bob


>
> -b
>

Re: RFC

[Smith, Elliot]

[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]

On 10 November 2015 at 17:34, Bob Cochran <yocto@mindchasers.com> wrote:

> On 11/05/2015 04:26 PM, Brian Avery wrote:
>
>> 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?
>>
>
>
> I'm all for it, but can you please upgrade toaster to work with Django
> 1.8.6 at the same time?
>
> As you probably know, migrations are now integrated into Django and no
> longer require South.  I work with Django on a regular basis, and I seem to
> have less migration headaches these days, although I know part of my
> improved quality of life was getting away from MySQL and moving to
> postgresql.
>
>
I am currently working on upgrading to Django 1.8; you can track progress
at:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=8364

Elliot
-- 
Elliot Smith
Software Engineer
Intel Open Source Technology Centre

[-- Attachment #2: Type: text/html, Size: 2038 bytes --]

RFC

[Scott@Charter]

[-- Attachment #1: Type: text/plain, Size: 212 bytes --]

I'm a Solaris guy trying to learn the differences between Linux and Solaris.
One of the things I'm hearing about is what's referred as RFC's.  Can anyone
explain to me what RFC's are?

Thanks,

Scott  -  Reno,NV

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Scott Smallsreed.vcf --]
[-- Type: text/x-vcard; name="Scott Smallsreed.vcf", Size: 366 bytes --]

BEGIN:VCARD
VERSION:2.1
N:Smallsreed;Scott
FN:Scott Smallsreed
TEL;HOME;VOICE:775-849-8411
TEL;HOME;FAX:775-849-8412
ADR;HOME:;;3030 Chipmunk Dr.;Washoe Valley;Nevada;89704;US
LABEL;HOME;ENCODING=QUOTED-PRINTABLE:3030 Chipmunk Dr.=0D=0AWashoe Valley, Nevada 89704=0D=0AUS
EMAIL;PREF;INTERNET:scott.smallsreed@mindspring.com
REV:20040401T035403Z
END:VCARD

Re: RFC

[Pitichai Pitimaneeyakul]

On Wed, Mar 31, 2004 at 07:54:03PM -0800, Scott@Charter wrote:
> From: "Scott@Charter" <scott.smallsreed@charter.net>
> To: "Linux-Admin-Group" <linux-admin@vger.kernel.org>
> Subject: RFC
> Date: 	Wed, 31 Mar 2004 19:54:03 -0800
> X-Mailer: Microsoft Outlook Express 6.00.2800.1158
> X-Mailing-List: 	linux-admin@vger.kernel.org
> 
> I'm a Solaris guy trying to learn the differences between Linux and Solaris.
> One of the things I'm hearing about is what's referred as RFC's.  Can anyone
> explain to me what RFC's are?
> 
> Thanks,
> 
> Scott  -  Reno,NV

RFC = Request for comments. RFC is set of technical document note about internet.
For example if you look for feature of DHCP server, there is a RFC document which include standard, and requirement 
for DHCP.  Think RFC is internet Draft before turning to be standard. 



-- 
+AU