Re: [cross-project-issues-dev] Managing repositories referenced by simre

[David M Williams <david_williams@xxxxxxxxxx>]

It is important to make sure the b3aggrcon
files point to something that allows a "quick last minute rebuild"
to be performed, if needed ... but beyond that, there's no specific rule
or guideline about how or when to do it ... I think it depends on each
project's (or release engineer's?) confidence in make the a quick, seemless,
highly reliable transition. In other words, some projects update the b3aggrcon
file to point to final locations, and remove the old locations, before
the release date ... others leave the old in place and don't change the
aggrcon file until after 6/27 "just in case. But, then they should
shortly after the release.  

To summarize ... or repeat ... 

It is fine to update the b3aggrcon file
during quiet week, to point to an equivalent (final) repo if you'd like
to do it "early" so you can get rid of "old" copy.
Ideally, those that do this,  would use the "Validate Aggregation"
function from their own local b3 aggregator editor to make sure there are
no typos or anything. 

It is important to make sure the b3aggrcon
files point to something that allows a "quick last minute rebuild"
to be performed, if needed.

HTH




From:      
 "Konstantin Komissarchik"
<konstantin.komissarchik@xxxxxxxxxx>
To:      
 "'Cross project
issues'" <cross-project-issues-dev@xxxxxxxxxxx>, 
Date:      
 06/12/2012 10:58 PM
Subject:    
   [cross-project-issues-dev]
Managing repositories referenced by        simrel
.b3aggrcon files
Sent by:    
   cross-project-issues-dev-bounces@xxxxxxxxxxx

---

I have a question regarding proper strategy
for managing repositories on the download server that are referenced by
simrel .b3aggrcon files.
 
I just updated Sapphire contribution to
reference [1], which is the final contribution but we aren’t officially
calling it final yet. Per Final Daze document, on 6-25, I will copy this
repository to [2] to make the release official. Then I’d like to clean
up old 0.5 pre-release downloads. How do I safely do that since RC4 is
still referenced by a .b3aggrcon file? Since further aggregator builds
aren’t expected, do I update .b3aggrcon file on 6-25 to point to [2] and
remove RC4 download? Do I wait until after 6-27 to do this?
 
Thanks,
 
- Konstantin
 
[1] : http://download.eclipse.org/sapphire/0.5.0.RC4/repository
[2] : http://download.eclipse.org/sapphire/0.5.0/repository
 
 _______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev