|Re: [cross-project-issues-dev] [Brainstorming] Why (not) a "Final Daze" in SimRel?|
On 27.06.2017 14:30, Mickael Istria wrote:
Yes, projects should just do this as good citizens to help keep the download server from being overloaded.
As I said, I just ignored this for EMF.
It could be a problem if your project depends on releases of other projects (because it depends on things new to that release), but the train with those bits isn't available yet...Â That's not the case for EMF so I don't worry about this...
Yes, learning it late is kind of bad.
I totally agree.Â It should be just part of building a good long-lived update site at Eclipse regardless of being on the train.
With discovery URLs and p2 update site touch points, that might well happen, yes.
Yes, if transparent mirroring helps the server that's great, but there's nothing better than having the server not be hit at all so that it can focus on serving up metadata and not be involved in artifact transactions at all, even in a minimal way.
I think it's probably more an issue of user confusion.Â It's certain conceptually easier for the user to see all projects released at once.Â And, as I said above, it's an issue of dependencies.Â The train is all about getting a consistent set of dependencies all in one place for one stop shopping.ÂÂ But in the end, projects can and some do release on their own schedules, independent of the train...
I can see why it's good practice to announce and make available all projects at once.Â If there are reasonable reasons that some projects not to do that, it shouldn't be a big deal.
Yes, the mirror stuff is just general best practice, and of course simple repositories need to be available to mirror them.Â So it's mostly an issue of when project releases become visible in composite repositories, i.e., in a "releases" composite.Â I can see some value in having all this happen at once, but it is a burden this time of year to make that happen.Â Dennis HÃbner does the releng work for EMF and I'm not going to make life more complicated for him.Â If it's easier to make this available earlier, I'm fine if he does that.Â I'm just grateful he does the work at all!!
Yes, I think it should be more of a guideline than a strict rule...
I think as a guideline it is good practice to make it all look coordinated, but if they're a source of stress, the project should do what's best for the project.Â But that's just my opinion. :-)