-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone,
Lots of people have expressed an urgent desire to have a stable version of portage that includes EAPI 2 support and automatic blocker resolution for cases like bug 244511. Since portage-2.2 isn't quite ready yet due to ongoing work in package sets and preserve-libs, and I don't want ongoing work to hold back other features that are stable, I'm planning to split a 2.1.6 branch from trunk. This branch will have package sets and preserve-libs support disabled. This branch will be named 2.1.6 in order to preserve continuity such that the final portage-2.2 release will have all of the features that have existed in previous portage-2.2 releases. In order to get testing on the new 2.1.6 branch, I plan to put portage-2.2 back in package.mask until portage-2.1.6 has been marked stable. Does this plan sound good? Are there any objections or suggestions? - -- Thanks, Zac -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkkU0YUACgkQ/ejvha5XGaOSfgCg7OVXmAPj48uaNpZ30NteH/DH QzMAoNHOHklCppYWUJn5oMUR//2Xu5hp =w6Wo -----END PGP SIGNATURE-----
