Re: [mylyn-integrators] updated project plans

[Alvaro Sanchez <alvsan09@xxxxxxxxx>]

Steffen,
Please see the answers embedded below,
Let us know how you would like to proceed.

/Alvaro

On Mon, Oct 17, 2011 at 1:09 PM, Steffen Pingel
<steffen.pingel@xxxxxxxxxxx> wrote:
> 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?
>

R4Eclipse has participated in the Eclipse New Products Showcase at
Eclipsecon 2010,
and was also presented in the Eclipse Demo Camp 2010 in Montreal,
We have received valuable feedback and a positive response. See the
R4Eclipse mention in the following article.
http://www.eclipse.org/org/press-release/20110324_showcasewinners.php?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+eclipse%2Ffnews+%28Eclipse+Foundation+News%29

We are scheduled to participate in Eclipsecon Europe 2011, this will
be a good opportunity to show the existing capabilities, and future
plans to interested users.

R4Eclipse has not been released yet and the publicity has been
limited. This shall change as we move to our fist release.
e.g. News and Noteworthy shall be created as we start producing
regular releases.

> 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.
>
Agree, the proposal to include R4E in a first release within Mylyn 3.7
will allow us to provide a realistic installation environment with all
dependencies available in the same site.

> 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.
>
Agree, we don't yet comply with all the requirements for the
simultaneous release, although we can schedule the activities and be
ready for the release in February.
Good progress has been done to comply with the Eclipse UI guidelines
and a UI review shall follow.

> 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?
>
This is the next feature to tackle in our backlog and we would like to
propose alternatives before the end of the month so we can discuss
them early November, we could for instance start discussions face to
face at Eclipsecon.

> 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.
>
I see the problem,  we can leave the Subclipse connector out of the
Mylyn Versions release for the time being.
would the Eclipse Market place be a suitable place to offer an
update site for the Subclipse connector and dependencies ??
We are also planning to produce a Subversive connector at a later
point which would be a valid alternative for SVN users.

> Thoughts?
>
> Steffen
>
>
> On Fri, Oct 14, 2011 at 5:28 PM, alvaro sanchez <alvsan09@xxxxxxxxx> 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
>> <steffen.pingel@xxxxxxxxxxx> 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
>>> mylyn-integrators@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/mylyn-integrators
>>>
>> _______________________________________________
>> mylyn-integrators mailing list
>> mylyn-integrators@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/mylyn-integrators
>>
>
>
>
> --
> Steffen Pingel
> Committer, http://eclipse.org/mylyn
> Senior Developer, http://tasktop.com
> _______________________________________________
> mylyn-integrators mailing list
> mylyn-integrators@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylyn-integrators
>