[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mylyn-context-dev] Juno SR1 MFT contribution
|
That sounds good and is how we handled categorization in the past. I
agree that we should only categorize features that user may want to
install such as the Papyrus or Ecoretools integration. Not sure that
also applies to UML2?
In regard to the SDK feature I would prefer if it wasn't categorized
since it's target at integrators rather then end users.
Steffen
On Fri, Sep 21, 2012 at 11:09 AM, Miles Parker <miles.parker@xxxxxxxxxxx> wrote:
>
> An embarrassed note that while I got the addition of Papyrus and UML2 support into Juno SR1, I neglected to add them to the collaboration category. By the time that change was tested, the train had left the station. So they can be consumed from there, and users can install, but only after unchecking the "Group Items by Category" box. I'm updating the Wiki to reflect that.
>
> On the same note, I've put in the fix for that and will do Kepler next. I'm thinking that we really only want the consumer (e.g. Ecoretools, UML2 and Papyrus) and SDK features listed there and not the ones that are useless by themselves (EMF and GMF). Make sense to everyone?
>
> -Miles
>
>
> ______________________________
> Miles T. Parker
> Senior Solutions Architect
> Tasktop
> http://tasktop.com
> Committer, Eclipse Mylyn and Virgo
> Project Lead, Model Focussing Tools and AMP
> http://milesparker.blogspot.com
>
>
>
>
> _______________________________________________
> mylyn-context-dev mailing list
> mylyn-context-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/mylyn-context-dev
--
Steffen Pingel
Principal Software Engineer, Eclipse Mylyn
Mylyn Tasks Lead
http://tasktop.com
