On 15-11-10 10:44, Tom Hobbs wrote:
Segmenting the JARs and changing the namespaces are two very big chunks of work. Both of which are going to have an impact on our users. (Let's not forget the user list!)
So this means publicity or announcing the change. And a roadmap item on the website for users only focused on download.
My reluctance to spread the namespace change over a number of builds is simply due to the work we then place on our users. If, after each release, they need to refactor and/or retest their own code (which might be an extensive task) then asking them to do that multiple times is a big ask. Warning them that in X months times, if they want to continue using River, they're going to have to go through one big hit of pain is (in my perhaps flawed opinion) a better approach.
+1 For a user, one session of fixing the imports should be the limit. Gr. Sim -- QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
