Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] I am wondering why some "project repos" are different than what's in "staging"?

Hi David,

Thanks for bringing this up. In the case of Gyrex, the link in our b3 aggregation file points to our composite repository of stable builds. I did do a rebuild as I was testing some stuff but that is not required to be picked up by the aggregation repo. The plan is to update the b3 file with the link to our release build once that is available. That will be the same content (but rebuild) we contributed to RC4.


Am 15.06.2014 um 19:09 schrieb David M Williams <david_williams@xxxxxxxxxx>:

It appears GMF, Gyrex, and XWT (at least) have changed their project repo contents after the final Luna build. And this was only a few days after the final build last Wednesday ... I am not sure what it would look like right now. This is disturbing for a number of reasons, and will require that we put a higher priority on changing some of the processes we follow. Details are in

But, I would like leads of GMF, Gyrex, and XWT to respond in the bug, to explain what's different, and why it was changed. That's not to say we are going to change Luna's staging repo, since no one asked for it, but I'd like to better understand where communication has 'broken down'. Has the purpose of the "aggregated repository" been forgotten (or, misunderstood)?

cross-project-issues-dev mailing list

Gunnar Wagenknecht

Back to the top