I also think it should be pruned. However:
1- I don't think that now is the time to do it. We already have a big challenge (the whole namespace issue, regardless of big bang or incremental approach).
2- The already long delay is going to push developers away - going on a discussion about pruning will certainly delay things substantially.
3- We are already facing rejection because of the delay, the namespace issue will also be a factor working against us and pruning will make things worse.
Pruning MUST come with an upside, which is delivering more updates and/or faster. If we do it now, no upside will be perceived. Also, we will be putting a big deal breaker for anyone that wants to try the new stuff.
I mentioned pruning before and I think that we should allow automatic migration to the new namespace as much as possible BEFORE start pruning. This way we can allow a smooth transition and only then we can start pruning. And honestly, I think the version after the next one would be the best candidate for pruning so we can shorten the period and deliver features that are likely to be out on this one because it's already taking so long.
And I don't think we should prune without a "frozen" period first, while stuff still works but no enhancements are being made. This will allow some time for applications to be adapted. Migrating with the big bang approach will allow us to do just that. We keep everything working, deliver some enhancements, tag some specs for pruning as a reason for not getting enhancements and we will have between the upcoming version and the following one to adapt applications before pruning.
Cheers.
P.S.: What do you say to the breaking backward compatibility? Not today. (GOT reference - sorry, I couldn't help myself).
Peter P. LupoSoftware Engineer, M.Sc.Certified ScrumMaster / Sun Certified Associate for Java PlatformMPS.BR Authorized Appraiser and Implementation Practitioner+1 647-676-3699http://www.pplupo.com