Thanks for raising that. Before we consider including R4E in the Mylyn release train I would like to better understand how much community feedback has been received for R4E and how much hardening has been done? While it's often challenging to encourage feedback for new components the interactions in Bugzilla, mailing lists, the news group and other channels are have been key to drive continuous improvement of Mylyn. From my experience blog posts, tweets, regular new & noteworthy updates and responsiveness on community channels are good vehicles to engage users to try out new components. Has there been much publicity of that nature around R4E?
This initial feedback from early adopters is particular important to work out common installation and compatibility issues. We make an effort to run automated tests in a number of environments and encourage committers to bootstrap on a variety of configurations. Still, we can only ever capture a fraction of the configurations that are deployed in the real world and rely on the community to validate builds before distributing releases to a larger audience and less experienced users. Another item that I would like to consider as part of the discussion is compliance with the Eclipse release train requirements and UI guidelines. We identified some areas for improvement in the last R4E UI review and I am not sure that all Juno requirements are already satisfied? Generally, all components that are part of the main Mylyn distribution should adhere to these standards. Furthermore, my sense is that Mylyn users have come to expect a high level of integration between Mylyn components. We discussed several possibilities, e.g. Task List integration, that could well for R4E. Has there been progress on this already? Regarding the Subclipse connector, I have a major concern that a successful installation requires adding external update sites. As discussed on the call a few weeks ago I'm leaning towards suggesting a policy that requires all Mylyn release train dependencies to be available from the Eclipse release train repository. In the case of the Subclipse connector, an external update site that links in all dependencies or an extension listing in discovery for instance could provide a much better install experience. Thoughts? Steffen On Fri, Oct 14, 2011 at 5:28 PM, alvaro sanchez <[email protected]> wrote: > The R4E team would like to participate in the Mylyn 3.7 release train > (as a First release) > > For Mylyn Versions I would suggest to add the Subclipse connector, and > document the dependency for the release of > 351840: [Subclipse] Subclipse blocks Mylyn tests > https://bugs.eclipse.org/bugs/show_bug.cgi?id=351840 > > Please let me know in case there is a need for additional information > /Alvaro > > > On Fri, Oct 14, 2011 at 7:31 AM, Steffen Pingel > <[email protected]> wrote: >> I have updated the project plans for Mylyn 3.7: >> http://www.eclipse.org/projects/project-plan.php?projectid=mylyn . >> Please take a look and let me know if anything is missing or >> incorrect. >> >> To add items to the plan: Set the "plan" keyword on the corresponding >> bug and schedule it for for 0.9/1.6/3.7. Bugs with a priority of P1 >> and P2 show under committed, bug with a priority of P3, P4 and P5 show >> under proposed. >> >> To add items to the backlog to consider them during planning: Set the >> "plan" keyword and schedule the bug for ---. >> >> Steffen >> >> -- >> Steffen Pingel >> Committer, http://eclipse.org/mylyn >> Senior Developer, http://tasktop.com >> _______________________________________________ >> mylyn-integrators mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/mylyn-integrators >> > _______________________________________________ > mylyn-integrators mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/mylyn-integrators > -- Steffen Pingel Committer, http://eclipse.org/mylyn Senior Developer, http://tasktop.com _______________________________________________ mylyn-integrators mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/mylyn-integrators
