Issue tracking

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue tracking

grampajohn
Administrator
I have written a draft process for project issue-tracking. Please read the section on issue tracking in the server wiki. The important points are to use the issue system effectively for both understanding and communicating what needs to be done and fixed, and for communicating plans and estimates of completion to assist with project planning.

As always, your comments are welcome. Also, note that one of the issue categories (the green tags) is "Process" - please use these to raise issues about how we could work together more effectively.

Thanks for your participation in this important process.

John
Reply | Threaded
Open this post in threaded view
|

Re: Issue tracking

grampajohn
Administrator
I did not finish that last note.

In order to get the process started, I would like everyone who has assigned issues to look at them, and either write up (in the form of a comment) your plan and a completion estimate, otherwise add a comment about why you are currently unable to make progress. If this means there are other unrecognized issues, we can add them; otherwise, it may be necessary to rearrange issue priorities to ensure that the blocking issues are moved up.

Thanks again.

John
Reply | Threaded
Open this post in threaded view
|

Re: Issue tracking

ddauer
In order to give a completion estimate, we need release dates for 0.12 and up as well as a clarification on what should happen with issues from 0.9/0.10 that have not been resolved yet.

David

On Thu, Feb 24, 2011 at 7:02 PM, grampajohn [via Power TAC Developers] <[hidden email]> wrote:
I did not finish that last note.

In order to get the process started, I would like everyone who has assigned issues to look at them, and either write up (in the form of a comment) your plan and a completion estimate, otherwise add a comment about why you are currently unable to make progress. If this means there are other unrecognized issues, we can add them; otherwise, it may be necessary to rearrange issue priorities to ensure that the blocking issues are moved up.

Thanks again.

John



If you reply to this email, your message will be added to the discussion below:
http://power-tac-developers.975333.n3.nabble.com/Issue-tracking-tp2569267p2569340.html
To start a new topic under Power TAC Developers, email [hidden email]
To unsubscribe from Power TAC Developers, click here.

Reply | Threaded
Open this post in threaded view
|

Re: Issue tracking

grampajohn
Administrator
Our initial attempt to schedule release dates has not been a big success, because the tickets have not been getting done. That can work in an environment with full-time personnel, but our availability has been somewhat unpredictable. Therefore, Clemens and I thought we would try to do it the other way around. Basically, what I want to try is to focus on raising the most important issues to the top, working them from the top, and doing a release when it makes sense.

Part of the original motivation for a tight release schedule was the assumption that all the plugins had to be packaged in each of these versions in order to make progress on other plugins, due to the dependency-resolution process in Grails. But that's not really a constraint. It works better, and the process is much more fluid, if we work with local dependencies until we have stable components. It just means you have to have local copies of all the plugins that have not been released recently enough to support your work.

So for the time being, I think it makes sense to decide on a case-by-case basis when a component is sufficiently stable to warrant packaging it as a downloadable plugin. The important milestones are the ones visible to partners who want to build brokers for the 2011 pilot competition. Let's focus on getting to the point where we can put a realistic date on an initial release for them.

Make sense?

John
Reply | Threaded
Open this post in threaded view
|

RE: Issue tracking

Wolf
Administrator

Yes, this makes a lot of sense to me.

 

Cheers,

 

Wolf

 

From: grampajohn [via Power TAC Developers] [mailto:[hidden email]]
Sent: Thursday, February 24, 2011 11:49 PM
To: Wolf Ketter
Subject: Re: Issue tracking

 

Our initial attempt to schedule release dates has not been a big success, because the tickets have not been getting done. That can work in an environment with full-time personnel, but our availability has been somewhat unpredictable. Therefore, Clemens and I thought we would try to do it the other way around. Basically, what I want to try is to focus on raising the most important issues to the top, working them from the top, and doing a release when it makes sense.

Part of the original motivation for a tight release schedule was the assumption that all the plugins had to be packaged in each of these versions in order to make progress on other plugins, due to the dependency-resolution process in Grails. But that's not really a constraint. It works better, and the process is much more fluid, if we work with local dependencies until we have stable components. It just means you have to have local copies of all the plugins that have not been released recently enough to support your work.

So for the time being, I think it makes sense to decide on a case-by-case basis when a component is sufficiently stable to warrant packaging it as a downloadable plugin. The important milestones are the ones visible to partners who want to build brokers for the 2011 pilot competition. Let's focus on getting to the point where we can put a realistic date on an initial release for them.

Make sense?

John


If you reply to this email, your message will be added to the discussion below:

http://power-tac-developers.975333.n3.nabble.com/Issue-tracking-tp2569267p2571407.html

To start a new topic under Power TAC Developers, email [hidden email]
To unsubscribe from Power TAC Developers, click here.



Disclaimer
De informatie verzonden in dit e-mail bericht inclusief de bijlage(n) is vertrouwelijk en is uitsluitend bestemd voor de geadresseerde van dit bericht. Lees verder: http://www.eur.nl/email-disclaimer.

The information in this e-mail message is confidential and may be legally privileged. Read more: http://www.eur.nl/english/email-disclaimer.