[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[corona-dev] FW: [mylar-dev] another short talk about Mylar at EclipseCon
|
I thought this would be interesting to Corona developers so I am cross
posting this entry from Mylar-Dev
Do we have "other ideas"? Eugene mentions workflow (receive task,
investigate, fix - it seems like completion of these items would be
interesting events. Are Corona Events a first step?
Linking projects to task repositories seems like it would benefit Corona
Project Containers. We probably want an API to be exposed.
Lets discuss and see if there are any items we should add to the bug.
Glenn
-----Original Message-----
From: mylar-dev-bounces@xxxxxxxxxxx
[mailto:mylar-dev-bounces@xxxxxxxxxxx] On Behalf Of Eugene Kuleshov
Sent: Saturday, January 13, 2007 8:46 PM
To: Mylar developer discussions
Subject: [mylar-dev] another short talk about Mylar at EclipseCon
I've submitted another short talk for EclipseCon: Team version control
mashup with Mylar. The intention is to discuss integration point between
Mylar and Platform Team support for version control systems (CVS and
Subclipse), such as:
-- Automatic task-specific change set management
-- Linking projects to the task repositories
-- Opening Corresponding Tasks for CVS and SVN (Subclipse) from standard
Team
Synchronize and History views
-- Applying patch from the attachments section in the task editor
-- Other ideas, i.e. support of development workflow (receive task,
investigate,
fix, commit and resolve issue).
Please vote or comment at
http://eclipsezilla.eclipsecon.org/show_bug.cgi?id=3999
regards,
Eugene
_______________________________________________
mylar-dev mailing list
mylar-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mylar-dev
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.