On 11/15/2010 2:45 AM, Peter Firmstone wrote:
Sim IJskes - QCG wrote:
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.
+1
Not only does doing it all at once reduce the number of releases
involved, it makes the user response to the rename much simpler. It is
easier to write scripts for a rename of all packages with one or two
prefixes than to pick out individual packages. It is easier to remember
"com.sun.jini has been replaced by org.apache.river" than to remember a
series of package changes.
That makes sense, these namespaces have been advised as subject to change.
Let me finish sorting the failing qa tests first though.
I think the fix for that should be part of the minor release to fix bugs
that comes next, before the package rename.
Patricia
