| Summary: | define top-level Mylyn project update site structure and feature decomposition | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Mik Kersten <mik.kersten> | ||||
| Component: | Mylyn | Assignee: | Mik Kersten <mik.kersten> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | b.muskalla, caniszczyk, shawn.minto, steffen.pingel, wayne.beaton | ||||
| Version: | unspecified | ||||||
| Target Milestone: | 3.5 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 337545 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Mik Kersten
*** Bug 336285 has been marked as a duplicate of this bug. *** This looks good to me. Additionally, Frameworks & SDK would end up with Mylyn Context SDK. The only thing that I find a bit confusing is the name of the "Mylyn Incubator" category. The listed features are not part of the Mylyn Incubator project and other Incubating features are listed in categories not marked Incubation so it's hard to see where the split is. How about "Mylyn Extra Connectors"? As outlined in bug 317913#c7 I would like to keep the actual Mylyn Incubator features on an entirely separate update site like we have done in the past. The other thing we need to be think through is the names of "Eclipse EGit" changing to "Mylyn EGit". I'm happy with whatever the EGit/JGit teams want here, I don't think it needs to be perfectly consistent, but I wrote it up that way and think that the list under "Mylyn Features" makes it clear what Mylyn has become. Created attachment 189771 [details]
screen shot
I have updated the categories and feature names as shown in the screenshot. I made some adjustments to the original proposal to maintain the current sort order of categories: Mylyn Features, Mylyn Integrations, Mylyn SDKs and Frameworks. For now the Builds and Reviews framework features are listed in the SDK category. These features are not useful unless a connector is installed and I don't want users to easily get into a scenario where they have an empty Builds view and no easy way to get the Hudson integration. I would suggest that we move the features to the top category once we have a proper discovery integration that supports simple installation of connectors. R4E and TBR are not yet included (see http://dev.eclipse.org/mhonarc/lists/mylyn-reviews-dev/msg00357.html). One more thing: The Commons, Context and Tasks SDKs are not yet available as separate features but all combined in the Mylyn SDK. Steffen: Looks good. I wonder if we should take off the "(Required)" and "(Recommended)" tags. Thanks for the feedback. I have removed the "Required" and "Recommended" qualifiers. We can reconsider if this turns out to confuse users. |