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. Regards, Christian _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
