Providing patches
I have the eclipse client connected to Jazz.net.
What is the best way for me to provide patches or possible code change to
Jazz.net ?
Should I get the latest stream from the server and create a CVS patch ?
Or is thwre a better way to submit a patch for review ?
--
Christophe Elek
Serviceability Architect
IBM Software Group - Rational
What is the best way for me to provide patches or possible code change to
Jazz.net ?
Should I get the latest stream from the server and create a CVS patch ?
Or is thwre a better way to submit a patch for review ?
--
Christophe Elek
Serviceability Architect
IBM Software Group - Rational
One answer
Hi Christophe,
I'm not sure if the question is:
- what is the best way in the current Jazz infrastructure, or
- how can we create the best infrastructure for reviewing patches before delivery.
Anyway, here's what we do in Eclipse development:
1. Up to recently we would create a text patch and attach to a bugzilla record (in your case, a workitem) for review
2. Since recently, we have a separate repository branch we commit fixes to. They are later reviewed and if accepted, delivered to the production branch.
I'm not sure if the question is:
- what is the best way in the current Jazz infrastructure, or
- how can we create the best infrastructure for reviewing patches before delivery.
Anyway, here's what we do in Eclipse development:
1. Up to recently we would create a text patch and attach to a bugzilla record (in your case, a workitem) for review
2. Since recently, we have a separate repository branch we commit fixes to. They are later reviewed and if accepted, delivered to the production branch.