Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylyn-docs-dev] Mylyn Docs and p2 repository locations


that sounds like a good plan. One thing I'm wondering is where maintenance releases are going to be published, e.g. 3.0.1? Would that override the 3.0 release or would there be a separate p2 repository? It's important that we have a stable p2 repository location for every release to enable consumer to point their builds at a specific release.


Agreed.  My thinking is that we would publish 3.0.2, 3.0.3, etc. all to the same p2 repository - in other words, when a point release becomes available the prior point release would be removed, but the location would stay the same.  So anyone pointing to the location would get the latest point release.

I believe it's a release train requirement to retain release repositories to ensure release train builds can be reproduced. Some consumers, e.g. Eclipse distributors, prefer to have stable repositories. We could consider appending the repositories but it might be easier to simply use a unique repository location for each release.
 

Mylyn also produces "integration" builds which is why the drops location exists. This makes is easy to provide multiple builds for a particular release stream. I assume WikiText will only be published to the nightly site and there is no need for integration builds or staging release builds?

I haven't heard of a need so far to provide multiple builds for a release stream.  It could be that I simply don't understand why they would be needed.  My plan right now is to not provide "integration" builds.  Should we adjust that plan?

That sounds fine to me. It implies that we could only contribute WikiText releases to the Eclipse release train (milestones) since the nightly site does not retain old versions.
 

Have you thought about how consumers would install WikiText builds into Eclipse? Mylyn provides composite repositories for each Eclipse release stream, e.g. http://download.eclipse.org/mylyn/releases/neon/ which makes it very simple for users to get the right version for their Eclipse installation. 

My suggestion would be to include the appropriate WikiText version in that composite site and assume that Mylyn Docs users will continue to use that as the source for installing WikiText into Eclipse. We can add a step to the WikiText release build to automate updating of those composite sites.

To be sure that I'm understanding correctly, are you suggesting that we continue to distribute Mylyn Docs for the EPP release train and other Eclipse installations via the Mylyn composite site?  

No, the release train is a separate issue. The aggregator build consumes artifacts from a specific drop location, e.g. currently http://download.eclipse.org/mylyn/drops/3.22.0/v20170222-0452 . We would need to add the Mylyn Docs repository to the mylyn aggregator file: http://git.eclipse.org/c/gerrit/simrel/org.eclipse.simrel.build.git/tree/mylyn.aggrcon .

If so, that sounds good to me.  I don't see a need to change it or for users to have yet another update site to worry about.

Some help on updating the composite sites would be really great.  Is there anyone interested in taking that on?

I can look into that.

Steffen

Back to the top