Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] aggregator files

> When should I update the WindowBuilder aggregator file?

Only when the "release" version is completely ready to use. That may be shortly after you do the move, but if you "leave it invisible" until release (like you are supposed to do) then p2 (and the aggregator) can't really use it yet. So, pretty much have to use "copy" (not move), leave the old one in place, and reference old one in b3aggrcon file, until the final resting spot is usable (visible to p2). Then you can update b3aggrcon file anytime after that. And, then, you can remove old RC4 directory.  Perhaps even all on "release day". There are some slightly different ways to do all this, if projects use composite repositories, but don't think that applies to you. Hopefully those that use composites, know what I'm talking about :) and know what to do.


From:        Mark Russell <mrrussell@xxxxxxxxxx>
To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:        06/08/2011 05:34 PM
Subject:        [cross-project-issues-dev] aggrigator files
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx

If I plan on moving my code to a new new location for release will I have to update the aggrigator file for WindowBuilder?

I currently have the code here:

the final resting place is:

When should I update the WindowBuilder aggrogator file?

Mark R Russell

(724) 473-3140
Release Engineer
Google Pittsburgh

cross-project-issues-dev mailing list

Back to the top