Ports tagging and branching
Joseph S. Myers
joseph@codesourcery.com
Tue Nov 17 13:31:00 GMT 2009
I propose that:
* ports should be tagged for 2.10.2 (tag glibc-2.10.2) at the current
revision of release/2.10/master.
* ports should be tagged for 2.11 (tag glibc-2.11), and branched for 2.11
branch (release/2.11/master), at the current revision of master.
* Further fixes for alpha, hppa and m68k required for those targets to
work be allowed to be cherry-picked to 2.11 branch even if they add new
symbols or otherwise would not be suitable for release branches for
targets already working on those branches (but if we reach 2.12
branchpoint without those targets having been made to work, such changes
should not go on 2.11 for them after that point).
--
Joseph S. Myers
joseph@codesourcery.com
More information about the Libc-ports
mailing list