[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [eclipse.org-architecture-council] Reminder: EAC meeting tomorrow at 11 EST

There was a typo in the bug ID.  The main bug is:

  291094: Do we really need 4 different ways to install adapters /
extensions
  https://bugs.eclipse.org/bugs/show_bug.cgi?id=291094

The following bug and its subtasks are also relevant:

  284501: support reuse of Mylyn Discovery by other tools
  https://bugs.eclipse.org/bugs/show_bug.cgi?id=284501

We're also in the process of formulating a proposal for moving Mylyn's
Discovery UI and mechanism to a more general home (eg, P2, EPP) and would
like to run that by the Architecture Council before submitting the bug.

Mik

--
Dr. Mik Kersten
CEO: http://tasktop.com
Lead: http://eclipse.org/mylyn
Follow: http://twitter.com/mik_kersten


> -----Original Message-----
> From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx
> [mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx] On Behalf
> Of Tom Schindl
> Sent: November-11-09 7:51 AM
> To: eclipse.org-architecture-council
> Subject: Re: [eclipse.org-architecture-council] Reminder: EAC meeting
> tomorrow at 11 EST
> 
> >     * Mik wanted to discuss install technologies along
> >       https://bugs.eclipse.org/bugs/show_bug.cgi?id=290094
> 
> Is that the real bug?
> 
> Tom
> 
> --
> B e s t S o l u t i o n . a t                        EDV Systemhaus
> GmbH
> -----------------------------------------------------------------------
> -
> tom schindl
> geschaeftsfuehrer/CEO
> -----------------------------------------------------------------------
> -
> eduard-bodem-gasse 5/1    A-6020 innsbruck      phone    ++43 512
> 935834
> _______________________________________________
> eclipse.org-architecture-council mailing list
> eclipse.org-architecture-council@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-
> council
> 
> IMPORTANT: Membership in this list is generated by processes internal
> to the Eclipse Foundation.  To be permanently removed from this list,
> you must contact emo@xxxxxxxxxxx to request removal.