Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [alf-dev] Eclipse ALF alternate bug tracking tool to consider forEclipseCon (or beyond)

Jagzilla http://jagzilla.sourceforge.net/ provides a web services api into Bugzilla.  IMHO, ALF should give highest priority to integrating the same tools that Eclipse itself uses in ALM (e.g., CVS and Bugzilla) in order to build community.


From: alf-dev-bounces@xxxxxxxxxxx [mailto:alf-dev-bounces@xxxxxxxxxxx] On Behalf Of Mirinda Lowe
Sent: Monday, March 06, 2006 2:28 PM
To: Alec Clews; ALF Developer Mailing List
Subject: [alf-dev] Eclipse ALF alternate bug tracking tool to consider forEclipseCon (or beyond)

 

Alec,

 

Thanks for the input.  Any thoughts on this option from the team?

 

Thanks

Mirinda

 


From: Alec Clews
Sent: Sunday, March 05, 2006 12:20 PM
To: Mirinda Lowe
Subject: RE: [alf-events] Eclipse ALF planning meeting minutes 3/3

Miranda,

 

Your item P2 below:

 

Here are a couple of options:  http://www.itracker.org/ or http://www.bestpractical.com/rt/features.html

 

IMHO RT would be a better choice (if technically feasible) because it has a much bigger mind share.

 

 

 

Regards

--

Alec Clews aclews@xxxxxxxxxx. Voice +61-(3)9522-4441

Consultant, Serena, Australia    http://www.serena.com/


From: alf-events-bounces@xxxxxxxxxxx [mailto:alf-events-bounces@xxxxxxxxxxx] On Behalf Of Mirinda Lowe
Sent: Saturday, 4 March 2006 7:07 AM
To: alf-events@xxxxxxxxxxx
Subject: [alf-events] Eclipse ALF planning meeting minutes 3/3

 

Attendees:  John Streiff, Bob Brady, Tim Buss, Steve Taylor, Brian Carroll, Christopher Rollo

 

Demo:

Request made to show BPEL flow as part of the recorded demo.  We are currently using the Oracle designer and may not have permission to show this.  Active BPEL designer is now free so we may want to consider switching to their designer.  Tim is looking into this further.

 

 

P1 - Replace Service Flow:

CVS - Have Steve's command line service flow -- need to try to call CVS from this.  Tim will try this.  Rollo working on installing the local client.  Team feels we also need to install Python.

 

Subversion - Mark Phippard working on getting this working with ALF.  The team needs to decide if everyone is okay giving him access to the machine (since everyone has their software installed here) or if Tim needs to do this set up for him.  Serena, Catalyst, Segue OK.  Secure needs to check with their legal and will get back to Tim.

 

 

P2 -Expected Build Failure & Submit Bug to Bugzilla:

Bugzilla does not appear to have any triggers, sends an e-mail when an issue is updated.  We would need to read these.  Not sure if we can easily include this by March 20 for EclipseCon. Tim thinks there is a Java interface bug tracking system that's compatible with Bugzilla - he's checking into this.  If anyone knows of any other open-source bug tracking systems that we might be able to plug in quickly, let the group know.


 

P3 - Branching for Test and Scan Options:

The test options are there.  TeamTrack has the options ready.  Need to implement the flow.  Added an option to scan or not scan.  Tim and John will work together to see if we add any more functionality to that.  This task is in good shape and we may add more sophisticated options to it as time allows.


 

P4 - Unexpected Build Failure:

Might create some sort of graphic to show how compensation works.

 

 

P5 - Service Stubs:

We'll look at starting this next week.  Secure & Catalyst have their required changes ID'd and they appear to be very straightforward.  

 

 

P6 - Corona:

No plan for a joint demo as there isn't sufficient time to create this.  Working to develop joint statements and possibly use cases.

 

 

P7 - VMware image for POC partners:

Tim e-mailed the partners on the process that we'll follow.  Will base this on the demo of EclipseCon so this will be ready at EclipseCon or shortly thereafter.

 

 

Note: All EclipseCon partners need to make sure their licenses are valid beyond EclipseCon.

 

 

Vocabulary Committees:

 

Steve is driving this effort.  Next step is to formalize the subproject structure and implement.  Also need to decide what tools we'll use and the approach for the use cases.  Team discussed whether there should be a formal subproject of Eclipse or ALF.  Steve will check into this.  Tim is starting in formal discussions on the source control vocabularies and use cases.

 

 

Team discussed the possibility of needing a Best Practices Guide for creating Web services.  We currently have a Conformance document already.  We could expand this if folks have more information.  Possibly having a one or two page Quick Start Guide would be a good idea.  If you have any suggestions for this please e-mail them to the ALF dev list or post to the Newsgroup.

 

Team discussed the possibility of associating ALF with some of the more popular, visible Eclipse projects such as JDT, CDT, Web Tools Platform.  Possibly also other projects as they arise.  We may have more synergy with the plug-in projects.  If you have any ideas for this please e-mail them to the ALF dev list or post to the Newsgroup.

 

Catalyst has updated their Web Service to handle failures. 

 

Updated project plan is posted on the ALF site with the tasks for EclipseCon.

**********************************************************************

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.


Back to the top