Eric Belanger wrote

IMO, Plan 1 is the way to go as this is how we managed the qt3/qt upgrade.

there was a qt package and a qt4 during a certain amount of time before the switch to qt3/qt

Does anyone has an idea on how many packages in the repo currently works with or need python3.0? If that number is zero or very small, i don't know but as python 3 is not yet out it should be pretty close to zero.

we could update python to 2.6 and wait until that number increases before proceeding with Plan 1. That will reduce the number of rebuilds because we will be replacing rebuilds by package update that eventually would need to be done anyway.

yes and no. because the number will grow very slowly and there is no such big beast like kde to force the switch. (is there ?) why not wait until python 3.1 ? i really fear that a great number of software will break because they will try to use /usr/bin/python and except a python 2 to be there. What about the package in unsupported that will not be upgraded asap as the others in extra or core or community.