[eclipse.org-architecture-council] [Bug 167144] Should we have an org.ec

[bugzilla-daemon@xxxxxxxxxxx]

https://bugs.eclipse.org/bugs/show_bug.cgi?id=167144  
Product/Component: Community / Architecture Council

Martin Oberhuber <martin.oberhuber@xxxxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |martin.oberhuber@windriver.c
                   |                            |om
         AssignedTo|cross-                      |eclipse.org-architecture-
                   |project.inbox@xxxxxxxxxxx   |council@xxxxxxxxxxx
          Component|Cross-Project               |Architecture Council
         OS/Version|Windows XP                  |All




--- Comment #17 from Martin Oberhuber <martin.oberhuber@xxxxxxxxxxxxx>  2008-10-29 05:36:33 -0400 ---
The concept is related to the Nexus proposal
(http://wiki.eclipse.org/Nexus_Project), and the new development process which
allows project nesting. 

Making it easier to mix-and-match smaller units of functionality among
different projects is a very important point of Eclipse Architecture moving
forward. Orbit has been a step in this direction for 3rd party libs, and P2 has
been a step in this direction from an update/provisioning point of view (no
more features required).

In my opinion, one of the biggest things to consider here is aligning release
schedules of micro-components. Should there be overall Eclipse Train Dates for
each and every project? What if adopters Foo and Bar want different versions of
the same component? Releng process as well as provisioning for adopters also
play a role here, perhaps even community discussion channels unique to the
component.

Moving to Architecture Council since this seems the right place for such
discussions.


-- 
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.