r18015 - gnucash/branches - Create 2.4 branch

Phil Longstaff plongstaff at rogers.com
Mon Apr 6 15:06:22 EDT 2009 

OK.  I'll remove the 2.4 tag.

BTW, one change I want to make, but have held off, is changing 'src/backend/file' to 'src/backend/xml' which is much more descriptive (since sqlite3 will also save in a file).  I assume this would cause merge problems from trunk -> 2.2 branch, but are there other issues you can see?

Phil



________________________________
From: Christian Stimming <stimming at tuhh.de>
To: gnucash-devel at gnucash.org
Cc: Phil Longstaff <plongstaff at rogers.com>; Derek Atkins <warlord at mit.edu>
Sent: Monday, April 6, 2009 2:41:00 PM
Subject: Re: r18015 - gnucash/branches - Create 2.4 branch

Am Montag, 6. April 2009 02:48 schrieb Phil Longstaff:
> Yeah, you're right re dev't.
>
> At this point, I'm doing a bit of cleanup.  I needed to make a small change
> to fix 'make check'.  There's now another problem in 'make dist' in the
> python bindings.

That's all fine. Just as Derek I highly appreciate your initiative and 
stepping forward here in the development.

For now, I'd suggest you remove the 2.4 tag again, and as Derek suggested, 
create it again right before or after the 2.3.0 experimental release.

As for "development not necessarily for 2.3.x or 2.4.x": Yes, that's correct, 
but it is too early for this. For now I think we're fine with the policy "all 
code from trunk is targeted for 2.4.0", but this doesn't hold for "all 
features". We can very well switch off particular features in the 2.4 branch 
once it is created. This could be as easy as disabling a ./configure switch 
(e.g. for webkit), but keeping the code identical between trunk and the 
future 2.4 branch as long as possible will make development a whole lot 
easier.

Regards,

Christian

>
> Phil
>
>
>
> ________________________________
> From: Derek Atkins <warlord at MIT.EDU>
> To: Phil Longstaff <plongstaff at rogers.com>
> Cc: gnucash-devel at gnucash.org
> Sent: Sunday, April 5, 2009 6:44:34 PM
> Subject: Re: r18015 - gnucash/branches - Create 2.4 branch
>
> I'm not sure there's really enough development going on that would
> warrant doing it that way.  I can't think of anything that's under
> development in a dev branch that we'd want in trunk and not 2.4..
> However I can think of lots of stuff (e.g. stabilization bug fixes)
> that we'll definitely want to put have in 2.3/2.4 and trunk, so
> delaying the branch until as late as possible is always the right
> answer.
>
> I admire you being proactive, and I appreciate you taking the lead
> on the 2.4 release engineer!   Thank you.
>
> -derek
>
> Quoting Phil Longstaff <plongstaff at rogers.com>:
> > I was using the development model that anything could go into trunk but
> > not necessarily into 2.3.x, so I created the branch to separate the
> > targeted 2.3.x development from the more general trunk development.
> >
> > Phil
> >
> >
> >
> > ________________________________
> > From: Derek Atkins <warlord at MIT.EDU>
> > To: Christian Stimming <stimming at tuhh.de>
> > Cc: gnucash-devel at gnucash.org
> > Sent: Sunday, April 5, 2009 4:27:59 PM
> > Subject: Re: r18015 - gnucash/branches - Create 2.4 branch
> >
> > Hi,
> >
> > Quoting Christian Stimming <stimming at tuhh.de>:
> >> Am Sonntag, 5. April 2009 01:45 schrieb Phil Longstaff:
> >>> Author: plongstaff
> >>> Date: 2009-04-04 19:45:29 -0400 (Sat, 04 Apr 2009)
> >>> New Revision: 18015
> >>> Trac: http://svn.gnucash.org/trac/changeset/18015
> >>>
> >>> Added:
> >>>    gnucash/branches/2.4/
> >>> Log:
> >>> Create 2.4 branch
> >>
> >> Err... this 2.4 branch is copied from trunk r18014, but you've already
> >> done further work on trunk which most probably should also be applied to
> >> any 2.4 branch there will be. Does this mean the 2.4 creation was
> >> prematurely? This is fine and it's okay to delete it for now and
> >> re-create (copy) later. Or did I miss some specific planning which was
> >> the reason to decide that trunk r18014 was a particularly good code
> >> state to start a 2.4 branch?
> >>
> >> IMHO if we indeed plan for a 2.4 release cycle in the near future, the
> >> branching from trunk to 2.4-branch will occur very shortly before the
> >> first release candidate (maybe numbered 2.3.x) will be released, but not
> >> earlier than that. To my knowledge, there isn't such an experimental
> >> 2.3.0 release planned in the near future, or is there?
> >>
> >> I'm asking because once there is indeed a 2.4 branch, I will have to
> >> take care to copy over all 2.2 (stable branch) translations on the new
> >> 2.4 stable branch. The trunk translations are (intentionally) much much
> >> older than the 2.2 translations, so starting a new stable branch will
> >> trigger some noticable overhead work on the translation side which needs
> >> to be done. It's fine with me to do this, but I need some clear
> >> communication about what is going to happen with the 2.4 branch.
> >
> > Yes, this branch is WAY premature..  WAY WAY WAAAAYYY premature.
> >
> > We need to have a series of 2.3.x releases off of trunk first and
> > then only cut 2.4 AFTER 2.4.0 (or maybe even after 2.4.1 or 2.4.2) once
> > we think there's enough "to be committed" work that would require
> > branching off.
> >
> >> Regards,
> >>
> >> Christian
> >
> > -derek
> >
> > --       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
> >      Member, MIT Student Information Processing Board  (SIPB)
> >      URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
> >      warlord at MIT.EDU                        PGP key available
> >
> > _______________________________________________
> > gnucash-devel mailing list
> > gnucash-devel at gnucash.org
> > https://lists.gnucash.org/mailman/listinfo/gnucash-devel
> > _______________________________________________
> > gnucash-devel mailing list
> > gnucash-devel at gnucash.org
> > https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>
> --       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>       Member, MIT Student Information Processing Board  (SIPB)
>       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
>      warlord at MIT.EDU                        PGP key available
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel

More information about the gnucash-devel mailing list