It's all about the answers!

Ask a question

What is the best practice to choose WIs and create baseline?

Bruno Braga (48013621) | asked May 12 '09, 5:06 p.m.
retagged Jun 24 '14, 11:11 a.m. by David Lafreniere (4.8k7)
Hi guys,

Our baselines (snapshots) were created directly in the stream (with the latest version of all files).
Now I'd like to choose some of the incoming activities and create a package (release) only with them. But I have some questions.

Implementation of tasks feature 1, feature 2 and feature 3.
These three tasks modify the same file web.xml, ok?

web.xml History:

The last snapshot baseline-feature1 has the feature 1 only.

So, I need to get baseline-feature1 and add the task feature 3 only, ok?
The task "feature 2" began to be developed first, but I dont want to add it to the package at this time.

After I load baseline-feature1 I see that:

Accepting feature 3:

The feature 3 was implemented after feature 2 and accept it alone will create a "Pending Patch". Its ok. But the merge "Pending Patches" into workspace will create a new version of web.xml (with feature 1 and feature 3).

I think I need to do checkin of this new web.xml to add it into a new baseline. But if I do that, this version will be the last version of the repository and it will be propagated to the team. If the developers accept this incoming, the changes in web.xml for "feature 2" will be deleted.

So what is the policy / best practice to generate a baseline with some (sub-set) workitems completed?

Accepted answer

10 other answers

permanent link
Bruno Braga (48013621) | answered Jun 24 '14, 11:38 a.m.
 David, nice to see that new feature ;)

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.