Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Trying to better understand/follow the process for the final Helios Service Release.


Thanks a lot for your answers... I think you only missed one...

What exactly is the "staging repository" ?.

... and new questions come up ;P

As conclusion the recommendation is:
1. Copying (and probably renaming) zips to the downloads release folder.
2. Copying my p2 repository from my maintenance repository to the releases repository and update the b3aggrcon file.... Since the repository doesn't change there is no any pain of breaking anything, providing I set the proper repository URL and the features versions in the b3aggr file... The features version shouldn't be changed (the same repo, then the same features with the same versions) I just need to be sure I set the URL of my final release repository (after doing the mov

The question which is not clear to me is when to do that ?. You mentioned "shortly before/after the final common aggregation build"... Do you mean RC4  (RC4 + 1, in my case) ?... Is there any other specific date for this?

The other question:

There's many twists, complications and nuances to make things easier or harder, so be sure to ask or look at other examples if things are not clear. For example, especially final repositories should have a mirrorsURL attribute for their artifacts repo, they should have "download stats" attributes, if desired .. and I'm sure things I'm forgetting.
I don't have any knowledge about what to do with our final release repository... Do you know any wiki page to look into this topic ? Any tool/script available to do it ?.

Again, thank you very much for your time.

Best Regards,
Open Canarias, S.L.
Adolfo Sánchez-Barbudo Herrera
C/Elías Ramos González, 4, ofc. 304
Tel.: +34 922 240231

Back to the top