Plans to releases to baselines - missink link?

On 1/14/10 11:55 PM, Freddy wrote:

Hi

A question from someone beginning an RTC implementation:
1. I have a plan with a bunch of WIs planned for the iteration.
2. I complete the iteration(and hopefully all the WIs), making changes
in Jazz SCM and associating those changes to the WIs.
3. I run a build that includes all of those WIs
4. The build creates a snapshot

Now given the plan how do I see what the related build snapshot is? E.g
if my plan is called "Iteration 2.0.1", I can create a "release"
("2.0.1")from the build but there isn't anything in the plan itself that
connects the two right?

Maybe I didn't quite phrase that right, but hopefully that makes sense?

Thanks for any advice/comments

There isn't a way to connect a plan with a release. Usually, the release
is the result of working on a certain iteration (an indirect, virtual
link). Still, you can link the release by adding it to the overview page.


--
Cheers, Johannes
Agile Planning Team

The way to associate a release to a build is to create the release from
the build result itself. In particular, in the bottom left of the
Overview page of the build result editor, you will see an action named
"Create a release to associate with this build".

There is a piece of missing functionality here ... you cannot associate
a build with a planned release. So what you have to do is use the
action identified above to create a new release, and then archive the
previous planned release. The work item asking for this functionality
is 57136. Please feel free to add your support for this enhancement by
subscribing to that work item and adding your comments.

Cheers,
Geoff

Freddy wrote:

Hi

A question from someone beginning an RTC implementation:
1. I have a plan with a bunch of WIs planned for the iteration.
2. I complete the iteration(and hopefully all the WIs), making changes
in Jazz SCM and associating those changes to the WIs.
3. I run a build that includes all of those WIs
4. The build creates a snapshot

Now given the plan how do I see what the related build snapshot is? E.g
if my plan is called "Iteration 2.0.1", I can create a "release"
("2.0.1")from the build but there isn't anything in the plan itself that
connects the two right?

Maybe I didn't quite phrase that right, but hopefully that makes sense?

Thanks for any advice/comments

Freddy

After reading Johannes' response, I reread the original message below,
and realized that the "plan" I was referring to was the list of "planned
releases", while what Freddy was asking about were the "iteration
plans". As Johannes said, currently, you would link an iteration plan
to a release by just adding a comment in page in the plan.

But then when you actually create the build for the planned release, you
will encounter the issue I describe below (:-).

Cheers,
Geoff

Geoffrey Clemm wrote:

The way to associate a release to a build is to create the release from
the build result itself. In particular, in the bottom left of the
Overview page of the build result editor, you will see an action named
"Create a release to associate with this build".

There is a piece of missing functionality here ... you cannot associate
a build with a planned release. So what you have to do is use the
action identified above to create a new release, and then archive the
previous planned release. The work item asking for this functionality
is 57136. Please feel free to add your support for this enhancement by
subscribing to that work item and adding your comments.

Cheers,
Geoff

Freddy wrote:
Hi

A question from someone beginning an RTC implementation:
1. I have a plan with a bunch of WIs planned for the iteration.
2. I complete the iteration(and hopefully all the WIs), making changes
in Jazz SCM and associating those changes to the WIs.
3. I run a build that includes all of those WIs
4. The build creates a snapshot

Now given the plan how do I see what the related build snapshot is?
E.g if my plan is called "Iteration 2.0.1", I can create a "release"
("2.0.1")from the build but there isn't anything in the plan itself
that connects the two right?

Maybe I didn't quite phrase that right, but hopefully that makes sense?

Thanks for any advice/comments

Freddy

I think what we're looking for is a formal or tighter way of doing what
Johannes' suggested - perhaps putting a URL to the build in the plan's
overview.
Can I ask how the Jazz/RTC teams deal with this ie. you have a plan say
"2.0.0.2" - now how do you identify a build or snapshot that identifies
what (in Jazz SCM) was delivered against that plan?

Regards
Freddy
Geoffrey Clemm wrote:

After reading Johannes' response, I reread the original message below,
and realized that the "plan" I was referring to was the list of "planned
releases", while what Freddy was asking about were the "iteration
plans". As Johannes said, currently, you would link an iteration plan
to a release by just adding a comment in page in the plan.

But then when you actually create the build for the planned release, you
will encounter the issue I describe below (:-).

Cheers,
Geoff

Geoffrey Clemm wrote:
The way to associate a release to a build is to create the release
from the build result itself. In particular, in the bottom left of
the Overview page of the build result editor, you will see an action
named "Create a release to associate with this build".

There is a piece of missing functionality here ... you cannot
associate a build with a planned release. So what you have to do is
use the action identified above to create a new release, and then
archive the previous planned release. The work item asking for this
functionality is 57136. Please feel free to add your support for this
enhancement by subscribing to that work item and adding your comments.

Cheers,
Geoff

Freddy wrote:
Hi

A question from someone beginning an RTC implementation:
1. I have a plan with a bunch of WIs planned for the iteration.
2. I complete the iteration(and hopefully all the WIs), making
changes in Jazz SCM and associating those changes to the WIs.
3. I run a build that includes all of those WIs
4. The build creates a snapshot

Now given the plan how do I see what the related build snapshot is?
E.g if my plan is called "Iteration 2.0.1", I can create a "release"
("2.0.1")from the build but there isn't anything in the plan itself
that connects the two right?

Maybe I didn't quite phrase that right, but hopefully that makes sense?

Thanks for any advice/comments

Freddy

To find the build/snapshot for the RTC 2.0.0.2 release, you would look
in the "Releases" tab of RTC, and select the artifact for the "2.0.0.2"
release. We therefore have no found no need for a hyperlink in the plan
itself (it's quicker to just go to the releases tab).

Cheers,
Geoff

Freddy wrote:

I think what we're looking for is a formal or tighter way of doing what
Johannes' suggested - perhaps putting a URL to the build in the plan's
overview.
Can I ask how the Jazz/RTC teams deal with this ie. you have a plan say
"2.0.0.2" - now how do you identify a build or snapshot that identifies
what (in Jazz SCM) was delivered against that plan?

Regards
Freddy
Geoffrey Clemm wrote:
After reading Johannes' response, I reread the original message below,
and realized that the "plan" I was referring to was the list of
"planned releases", while what Freddy was asking about were the
"iteration plans". As Johannes said, currently, you would link an
iteration plan to a release by just adding a comment in page in the plan.

But then when you actually create the build for the planned release,
you will encounter the issue I describe below (:-).

Cheers,
Geoff

Geoffrey Clemm wrote:
The way to associate a release to a build is to create the release
from the build result itself. In particular, in the bottom left of
the Overview page of the build result editor, you will see an action
named "Create a release to associate with this build".

There is a piece of missing functionality here ... you cannot
associate a build with a planned release. So what you have to do is
use the action identified above to create a new release, and then
archive the previous planned release. The work item asking for this
functionality is 57136. Please feel free to add your support for
this enhancement by subscribing to that work item and adding your
comments.

Cheers,
Geoff

Freddy wrote:
Hi

A question from someone beginning an RTC implementation:
1. I have a plan with a bunch of WIs planned for the iteration.
2. I complete the iteration(and hopefully all the WIs), making
changes in Jazz SCM and associating those changes to the WIs.
3. I run a build that includes all of those WIs
4. The build creates a snapshot

Now given the plan how do I see what the related build snapshot is?
E.g if my plan is called "Iteration 2.0.1", I can create a "release"
("2.0.1")from the build but there isn't anything in the plan itself
that connects the two right?

Maybe I didn't quite phrase that right, but hopefully that makes sense?

Thanks for any advice/comments

Freddy