I was reminded by one of our observant
Project Leads that this means it's a good idea to get any 2.0.2 code intended
for this week's M-build released before noon (Eastern time) on Wednesday
Besides the time to do the restructuring,
it'll take committers a while to get their workspace's set up again, so
... best not to leave to the usual "end of day".
If anyone has trouble/issues/questions
with this, be sure to let me know!
David M Williams/Raleigh/IBM@IBMUS Sent by: wtp-dev-bounces@xxxxxxxxxxx
11/13/2007 01:18 PM
Please respond to
"General discussion of project-wide or architectural issues."
[wtp-dev] Reminder that we are restructuring
CVS Wednesday afternoon
I'll start at 1:00 PM tomorrow, and will likely take about an hour, if
not several. I'll post a "done" message when it's ready.
As previously mentioned, this will require developers to create new workspaces
... or, at least, to get new WTP projects checked out, replacing their
old WTP projects.
So, be sure you have any "local" code saved away:
if small ready for HEAD, just check it into
if large changes, not ready to be committed
to head yet, you can create temporary branches with your changes, and they
will still be moved.
if you can't do either of the above, create
patch files, which you can later apply back to your workspace.
Remember, just exporting the java files, and
re-importing them is not a good technique, as this will cause the connection
to a files history to be lost, or reset.
You might also create Team Project Sets to capture your favorite projects,
as these can be updated with new repository locations to be partially automatic.
(I have not created those SED scripts yet, but plan to later today).
I'm sure there will be a few hiccups along the way, so appreciate everyone's
wtp-dev mailing list