Hi Christian, On Thu, 11 Sep 2014 15:59:53 +0200 Christian Kellermann <[email protected]> wrote:
> I have just merged the last master commits into chicken-5. Many thanks for doing that. > The idea is that we will do a final 4.10 release and then continue to > work on the chicken-5 branch which could be merged back into master > then. Alright. > So for newer patches you should base them on the chicken-5 branch. > Bugfixes worth of including into 4.10 will be backported from there. > > What do you think? I wonder if we should adopt that policy now. Until we have a well shaped CHICKEN 5, I was expecting patch submission to master (currently 4.x) and merging them into chicken-5. The rationale for this is: * We have a long road to CHICKEN 5 * CHICKEN 5 will be smaller, with less code, so it's easier to target CHICKEN 4 and remove code that don't apply to CHICKEN 5; than submit patches to CHICKEN 5 and backport them to CHICKEN 4 -- patches that target CHICKEN 5 may be incomplete for CHICKEN 4. Does that make sense? For the sake of clarity and organization, I propose that patch submissions exclusive for chicken-5 explicitly indicate that (e.g., in the subject header). Best wishes. Mario -- http://parenteses.org/mario _______________________________________________ Chicken-hackers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-hackers
