We already had calendar repositories (e.g., Outlook, Google Calendar) in Tasktop, but did not incorporate these into Mylyn’s Task Repositories view and API because one new kind of repository was not enough to justify broadening the API. With the new Atlassian tools, we now have Bamboo and Crucible repositories, which had a very large amount of overlap with Task Repositories like JIRA. So for last week’s Mylyn 3.1 release we ensured that the API could support these other kinds of repositories. For an example see the screenshot on the New & Noteworthy. For the Galileo-based Mylyn 3.2 we are thinking of changing the name of the Task Repositories view to “Team Repositories”, and categorizing it by repository kind, e.g., Tasks, Email, Calendars, Build Systems, Code Review.

The other interesting part is the overlap between the code review editor and the task editor. For the beta we managed to get some reuse and a consistent look, but we could not quite fit it into the task editor framework. I’m hoping that for Mylyn 3.2 we’ll be able make the task editor more flexible in order to better support new kinds of task editors of this sort. It’s the same story with Tasktop’s task editor for email threads. It’s still overriding a lot of behavior from the task editor instead of inheriting it, and we hope to improve on that for the next release.

This is exciting news.

You’ve mentioned “Mylyn API changes that Crucible and Bamboo are pushing”. Have these changes landed into the Mylyn repository? Also, is there any timeline for getting them released?

Thanks,

Robert

Thanks,
Ken