Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Please recommend a stream strategy

Questions
Tags
Users
Badges
Weilim Er
(46●1●20●13) Feb 10 '11, 1:38 a.m.
Company A implemented a system(ProjectA) and released it as ProjectA-1 (maintenance project). Over time, the number of releases and hence projects increased. Since all the projects are implementing the same system, a lot of codes are shared among the developers. They have a lot of trouble with managing and merging the codes in all these projects. Could you suggest a stream strategy and best practises to minimize the hassle of code merging in such a scenario?

0 votes

1 answer
4,339 views
0 votes

One answer

Permanent link
Michael Valenta
FORUM MODERATOR / JAZZ DEVELOPER (3.7k●3) Feb 10 '11, 9:10 a.m.
Typcially, the way we work is to have a stream per release. When we need to make a change that should appear in all releases (or a subset of releases), we make the change in the oldest release and forward port it to later releases that require it.

0 votes

Your answer

Register or log in 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.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Feb 10 '11, 1:38 a.m.

Question was seen: 4,339 times

Last updated: Feb 10 '11, 1:38 a.m.

Confirmation Cancel Confirm