Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] For Helios M5 we (probably) can not retain older milestone repositories

I wanted to give some (small) advance notice here (and make urgent plea for help, if anyone wants a different outcome) ...

Given bug 301201 [1], and to a lessor extent bug 299344 [2], I think the only (easy) course of action is to abandon the previous M2, M3, and M4 Helios repositories that we have been composing each milestone.

We began to 'compose' each milestone, because its important to do that composition release-to-release (according to previous discussions, see bug 291848).  

And, we have learned some important things about doing it for milestones, and have made improvements to make that work better correctly (e.g. see bugs 298566 [4], 301237 [5]).

But, we do not yet have good facilities for repairing or re-constructing repositories when they contain bad bundles. At least, as far as I can tell.
I have opened bug 301441 for the general issue.

The point of this cross-project posting it to give notice the Helios M2, M3, and M4 composite branches will not be maintained in M5, and M5 will "start fresh" ... unless someone is able to volunteer to fix the older repos in the next few days.



Back to the top