Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Mylyn is leaving the release train...

That's a very good point. We'll certainly aim to do the migration as quickly as possible to allow downstream consumer to integrate early. At the moment we are distributing a frozen copy of code that has been moved to Git as we are still in the process of updating the build accordingly. In terms of timing M6 is the worst case scenario but if the restructuring continues to progress well I expect that we will be able to provide builds against the latest sources much sooner and very likely for M5.

Steffen


On Wed, Dec 15, 2010 at 6:33 AM, John Arthorne <John_Arthorne@xxxxxxxxxx> wrote:
I don't work on projects downstream from Mylyn, so I am just asking this out of curiosity. If you are continuing to contribute the old Mylyn Tools content for M4 and M5, is that the same code that appears in the new sub-projects, or a copy that was frozen at the time of the migration to a top level project? Ie., will your M4 and M5 contributions contain all of your latest work, or will that only happen in M6 when you switch over to contributing your new projects? I'm asking because generally speaking, integrating earlier is usually better, so that any downstream projects and packages have time to react and adjust well before the final release.

John



Steffen Pingel <steffen.pingel@xxxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

12/15/2010 08:45 AM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

To
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc
Mik Kersten <mik.kersten@xxxxxxxxxxx>, Mylyn developer discussions <mylyn-dev@xxxxxxxxxxx>
Subject
[cross-project-issues-dev] Mylyn is leaving the release train...





... but fear not, the Mylyn Commons, Mylyn Context, Mylyn Docs and
Mylyn Tasks projects intend to join the Indigo release train.

The background is that Mylyn was recently promoted from a Tools to a
top-level project (bug 304957). In the process the project was
restructured and split up in a number of sub-projects (bug 328383)
some of which will be contributing to the train.

Nothing will change for consumer of Mylyn except for the repository
location which will move in the future. All released features will
keep their ids.

For M4 we'll leave everything as is and contribute as the "old" Mylyn
Tools project as all new sub-projects have Incubation status at the
moment. We plan to mature the sub-projects by M6 at the latest and
will switch repository locations at that point.

Please feel free to ask any questions or chime in on the discussion on this bug:

 328393: provision Mylyn sub projects
 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=328393

Steffen

--
Steffen Pingel
Committer,
http://eclipse.org/mylyn
Senior Developer,
http://tasktop.com

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev




--
Steffen Pingel
Committer, http://eclipse.org/mylyn
Senior Developer, http://tasktop.com

Back to the top