Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] webtools.jsdt project provisioned: what's next?


One thing that's next is the bugzilla components. The jsdt and _javascript_ that's in "WTP Source Editing" product can (and should) be "moved" to the new JSDT product. (I know, it's nice seeing "no bugs", eh? :)
The webmasters can help with that. Just open a bug under 'community', 'bugzilla' (I guess) and include 'provisioning jsdt' somewhere in the title. As for the "_javascript_" component, if it is not already, it can be marked as "read only" so searches still work (and all history maintained) but it wouldn't be offered as a component when opening a new bug.  As for "jsdt" component, I'm not sure it makes sense to have "jsdt" component in a "JSDT" Product, but ... I don't think they can be renamed (easily). You might leave that as a "general" one, and then create a few others for more specific areas, such as "editing", "debug", .... ?

Now for CVS. You should open a bug there, also under 'community', 'cvs', I guess (mentioning provisioning jsdt). Even if I end up issuing the commands to make the moves, we'll want webmasters aware of it, etc. FYI, we don't literally move, but copied, marked old ones read only, and deleted old ones a day or two later, after being satisfied all went ok.

To coordinate the CVS move takes a couple of things: 1) for builds, update map files (and this has to be done to all branches of map files ... any that are still active, or for which patches are produced). While you already have your own map files, in releng.jsdt, the "location" named in them needs to be updated.  2) All committers should get workspace code committed and synch'd up, since, basically, you'll need to delete what's in workspace, and re-checkout the new modules.

As for when to move cvs modules? I'd prefer to do it before M6, if not too disruptive to you. March 4 begins our "shutdown" week. I'd suggest we target a Friday, after declaring weekly I build. I think that leaves Feb
26 as a good target date?

From: Nitin Dahyabhai/Raleigh/IBM@IBMUS
To: wtp-dev@xxxxxxxxxxx
Cc: Simon Kaegi <Simon_Kaegi@xxxxxxxxxx>, Michael Rennie <Michael_Rennie@xxxxxxxxxx>
Date: 02/17/2010 10:35 AM
Subject: [wtp-dev] webtools.jsdt project provisioned: what's next?
Sent by: wtp-dev-bounces@xxxxxxxxxxx

"Webmaster(Matt Ward)" <webmaster@xxxxxxxxxxx> wrote on 02/17/2010 10:05:29 AM:
> From: "Webmaster(Matt Ward)" <webmaster@xxxxxxxxxxx>


> The webtools.jsdt project is all set up and ready to go!

JSDT has now been provisioned as its own project under WTP.  The next step would be to move the existing JSDT modules into the new location, but I'm pretty sure David handled the specifics of that when the WST and JST projects were first split (alternately, I wasn't paying attention that time or this really isn't the next step).  I'm guessing this is something we'd want to schedule very carefully, at least to keep the builds from failing at an inopportune part of the week?

And to our newest Committers, Simon and Michael, I believe the same question is in order?  How soon do you want to begin moving your modules in?

Nitin Dahyabhai
Eclipse WTP Source Editing
IBM Rational
wtp-dev mailing list

Back to the top