Community
Participate
Working Groups
With the number of Mylyn projects, releases, extension and supported Eclipse versions growing it gets increasingly more difficult for users to install matching version connectors or find the latest Mylyn version for their platform (see http://wiki.eclipse.org/index.php/Mylyn_FAQ#What_versions_of_Eclipse_are_supported.3F). Particularly when connectors use Mylyn internals and specify tight version constraints this can easily lead to failing installation. Another problem is that the current Mylyn update site is /updates/e3.4 and there are no corresponding sites for 3.5 or 3.6 which can be confusing. Also 3.4 support will be discontinued so this would get even more confusing with the next release. In order to simplify installations for users I suggest the following restructuring: (Composite) repositories that point to the latest Mylyn version for a particular Eclipse release. These are the locations advertised on the downloads page and in the EPP packages. The structure follows the releaes train, cdt and other Eclipse projects (one repository per major Eclipse version): /releases/helios /releases/indigo Discovery repositories for major Mylyn versions to ensure that connectors for older releases are always available (one repository per major Mylyn version): /update/3.4 /update/3.4/incubator /update/3.5 /update/3.5/incubator Composite repositories that reference the most recent Eclipse release train contribution: /update/helios /update/indigo Weekly integration builds: /update/weekly /update/weekly/incubator Integration builds for active service branch (e.g. 3.4.x builds if weekly site hosts 3.5 builds): /update/maintenance /update/maintenance/incubator Users would only be concerned with the /release update sites and the /update/weekly site. The others repositories would be managed through discovery and touchpoint operations that can add and remove sites for the corresponding release automatically.
As discussed on today's call, I would like to refine the proposal and suggest the following structure under download.eclipse.org/mylyn: /releases/3.4 - Release builds, point to the latest service release of the respective release /releases/3.5 /release/helios - Release train contribution /release/helios/staging - Stagged release train contribution /release/indigo /release/indigo/staging /release/latest - Most recent release build, convenience to always stay on the latest /snapshots/weekly - (Weekly) integration builds, manually triggered, signed /snapshots/nightly - Automated nightly integration builds /archive/3.4.1/v2011.../main - Actual release artifacts /archive/3.5/I2011...
Proposed categories: Mylyn Features Mylyn Task List (Required) Mylyn Task-Focused Interface (Recommended) Mylyn Integration Mylyn Bridge: C/C++ Development Mylyn Bridge: Eclipse IDE Mylyn Bridge: Java Development Mylyn Bridge: Plug-in Development Mylyn Bridge: Team Support Mylyn Connector: Bugzilla Mylyn Connector: Trac Mylyn WikiText Mylyn Plug-in Development Mylyn SDK Mylyn WikiText SDK Eclipse EGit - Sources (Incubation) Eclipse JGit - Sources (Incubation) Mylyn (Incubation) Eclipse EGit (Incubation) Eclipse JGit (Incubation) EGit Mylyn (Incubation) Mylyn Bridge: CVS (Incubation) Mylyn Connector: Hudson (Incubation) Mylyn Connector: Gerrit Code Review (Incubation) Mylyn Framework: Builds (Incubation) Mylyn Framework: Versions (Incubation) Reviews for Eclipse (Incubation) Task-Based Reviews for Mylyn (Incubation)
Steffen: This looks good to me for the current structure (though I needed to use View Unformatted Text to see the nesting). What would be helpful is if you could show me what it looks like in the UI, or post a screenshot. As part of a 1.5 review I want us to consider a clarification of our naming to make things more consistent across the features and the UI, so that might affect this naming. I created bug 335233 for that.
Created attachment 187458 [details] screenshot Here is a screenshot of the features currently available. Task-based Reviews, R4E and EGit are not yet included.
Created attachment 187802 [details] updated screenshot
Thomas Hallgreen pointed out that getfacl/setfacl can be used to allow hudsonBuild to write to the download location: build:~/downloads/tools/buckminster> getfacl . # file: . # owner: thallgren # group: tools.buckminster user::rwx user:hudsonBuild:rwx group::rwx mask::rwx other::r-x
I have thought about this more and iterated over the proposed directory structure. On the top level I would like to differentiate by quality expectation which seems common, e.g. for Maven repositories. Mylyn has three levels of quality: releases, snapshots and experimental. The second level separates by stream. This is either the underlying platform or Mylyn version for installing extensions. In theory the extension install could use archive sites directly but composite sites have the benefit of hiding the technical structure of the archive and provide a layer of indirection to manage content. Separating this by Mylyn version will guarantee that users are always able to find and install the connector versions compatible with their installed Mylyn version. The incubator features are only available under experimental and no longer part of releases. We will still make an effort to provide Incubator versions that are installable as widely as possible but guarantees are much weaker: Tests only run against the latest Eclipse platform, the experimental repository is updated less frequently etc. bc.. archive: - repositories for integration and release builds 3.5.0/ 3.5.0/I20110202-1522 3.5.0/I20110202-1522 releases: - composite repositories for latest releases by major and platform version 3.5 - latest 3.5.x release, used for connector discovery on Mylyn 3.5 galileo - releases compatible with Eclipse 3.5 helios - releases compatible with Eclipse 3.6 indigo - releases compatible with Eclipse 3.7 latest - latest release snapshots: - composite repositories for latest integration builds 3.5 - latest integration build of Mylyn 3.5, used for release train staging galileo - integration builds compatible with Eclipse 3.5 helios - integration builds compatible with Eclipse 3.6 indigo - integration builds compatible with Eclipse 3.7 nightly - nightly build weekly - latest integration build experimental: - Mylyn Incubator integration builds 3.5 - latest integration build compatible with Mylyn 3.5
Steffen: I created bug 336563 for the update site structure that we discussed on the last call.
The new update site structure is in place now.
