Bugzilla – Full Text Bug Listing
| Summary: | finalize webtools final release repository | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Releng | Reporter: | David Williams <david_williams> | ||||||
| Component: | releng | Assignee: | David Williams <david_williams> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | David Williams <david_williams> | ||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | kaloyan | ||||||
| Version: | 3.10 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
David Williams
Kaloyan, this was what I mentioned in last weeks status meeting as needing to coordinate with you. (I decided to open a bugzilla, instead of send email, like I said). Were you planning to have a final "releases" directory? And rename you RC4 to R? David, I thought I would copy the RC4 repository to a "releases" folder like: http://download.eclipse.org/libra/relases/R-0.1.0-201106071417/repository/ Then I will update the WTP Indigo repository. Does this sound OK for you? Do I need to update also the Indigo Aggregation build? I am not sure if this is necessary. In a few weeks, I am going to delete all Indigo milestone repositories. I have to check the WTP Retention Policy about this. (In reply to comment #2) > David, I thought I would copy the RC4 repository to a "releases" folder like: > > http://download.eclipse.org/libra/relases/R-0.1.0-201106071417/repository/ be sure to specify 'releases' correctly :) Though, honestly, don't know if you need "releases" for the main one? And, I'd recommend you "switch" 'repository' and the R directory. So you'd end up with .../libra/releases/repository/R-0.1.0-201106071417/ or .../libra/repository/indigo/R-0.1.0-201106071417/ (as a general naming rule, I try to follow "most specific part to the right"). That way, if there is, eventually, an SR1 or SR2 for it'd just be adding a subdirectory to /libra/releases/repository or /libra/repository/indigo and eventually /libra/repository/juno What URL is used in libra features? Just .../webtools/repository/indigo? If so, guess it doesn't really matter if you have "one URL" for all of libra. > > Then I will update the WTP Indigo repository. Does this sound OK for you? > Well, not really. That's kind of the point. We are not supposed to "make them visible" until the simultaneous release day. While probably no practical implications for the little libra project, I think its best to "get in the flow" and do things "simultaneously" ... that is, get things ready, and then update composites at the allotted time. One way to do that is to have one, coordinated ant script which does it all at once. The alternative is one of us could run a script for libra and someone else run it for (rest of) webtools (you do use a script, right?). Its not a big deal to do separately ... but ... I think ideal is to do "all at once". Of course, alternative three, if you'd prefer to run the one script that does both, that's all the better for me! :) > Do I need to update also the Indigo Aggregation build? I am not sure if this is > necessary. > Yes, this is necessary. We'll be starting maintenance and Juno builds soon ... so important it always be accurate/buildable. > In a few weeks, I am going to delete all Indigo milestone repositories. I have > to check the WTP Retention Policy about this. Yep, milestones can/should be removed, unless there's an exception requested. Created attachment 198294 [details]
makeComposite.xml
Updated Ant script with the Libra R-0.1.0 repository.
David, the URL of the R-0.1.0 release is: http://download.eclipse.org/libra/releases/R-0.1.0-201106071417/ There is also a composite repository pointing to the latest Indigo SR: http://download.eclipse.org/libra/releases/indigo/ I will update it when Indigo SR1 and SR2 are released. I updated the Indigo Aggregation build with the R-0.1.0-201106071417 URL. I see the Hudson job is currently disabled. I guess you should run it now. I attached new version of the makeComposite.xml that will add the R-0.1.0-201106071417 URL to the WTP Indigo composite repository. If you like to share the responsibility of clicking the big Indigo button, then it's not a problem to run this script. Just tell me the exact time when this should happen. Anything else left for Indigo? > I updated the Indigo Aggregation build with the R-0.1.0-201106071417 URL. I see > the Hudson job is currently disabled. I guess you should run it now. Not yet ... I usually leave disabled until after the release, so as not to confuse anyone, and many people do these sorts of update. (But, I do have a test machine, that'll complain if your new URL isn't right ... so I'll let you know :) > > I attached new version of the makeComposite.xml that will add the > R-0.1.0-201106071417 URL to the WTP Indigo composite repository. If you like to > share the responsibility of clicking the big Indigo button, then it's not a > problem to run this script. Just tell me the exact time when this should > happen. No need, I'll run it this Wednesday 9AM Eastern ... maybe you can do it for Juno ... 9 AM Eastern is actually a reasonable time, for you, eh? 4 PM? :) > > Anything else left for Indigo? Not that I can think of. For long term reference, I store the makeComposite.xml file in CVS, in /releng.wtpbuilder/manualStepScripts/antrunner/makeComposite.xml but, it is just for "storage" only .. there's nothing that automatically checks it out or runs it from there (currently). I actually "run" it from a shell script, under /shared/webtools/apps/antrunner ... just for future reference, if anyone ever needs to know ... or, if I get hit by a bus before Wednesday morning :/ I'll mark as fixed, since I have the file now, though won't actually run it till 6/22. Thank you very much. |