RE: New Subscriber

[Sequeira, Brian]

thanks for your feedback Gianni. Sounds good.

we currently do have a two week release period where developers work on changes & unit testing during QA cycle of previous release, then we default tag everything upto the next release after production push. Developers work on more defects and do SIT(Systems Integration Test), after release to QA we have some more builds till QA gives a green light for production push.

 

All of this development on a single CVS repository and in Interwoven we stage them into a release tag. To add to this mix we would have some parallel development for other projects but they would related to the web development as well i.e. we would integrate changes from those projects into the release. But without having to slow down the release cycle in any way.

 

Thanks

Brian

-----Original Message-----
From: Gianni Mariani [mailto:address@hidden
Sent: Monday, July 30, 2001 12:37 PM
To: Sequeira, Brian; address@hidden
Subject: RE: New Subscriber

 

The branching strategy that's best depends on the nature of the development.

 

What I find works in most cases is to:

 

1. Develop most features on the HEAD branch

2. Branch for releases when the HEAD becomes Beta quality

3. Branch for projects/features that can destabilize the tree for periods greater than 3 days.

4. Release branch modifications are merged into the HEAD when they are made.

5. Project branches are merged when a trial merge shows alpha level quality and usually just after a release branch is started.

 

What takes some thinking is when you've fixed a bug in the project branch and it's needed in a release branch.

 

For web sites, I've found it very effective to release every 2 weeks and target a release branch 1 week before release.

 

I'm sure there are other good strategies.  Nothing is fool proof.  You need to pick somthing that is the lesser evil for you.

 

G

 

-----Original Message-----
From: address@hidden [mailto:address@hiddenOn Behalf Of Sequeira, Brian
Sent: Monday, July 30, 2001 7:58 AM
To: 'address@hidden'
Subject: New Subscriber

Hello,

 

Just started my subscription to this mailing list. I work as a build/release engineer at my company. We use CVS and Interwoven for development purposes. Currently we do not do any branching here, and just develop of the main trunk and use the rtag option for releases.

 

We are planning to add two more projects along with our website development. Not sure if we need to add those projects with our web development and start branching our development, or to have different repositories for them in CVS and tag those projects separately. Any advice? Any strategy currently used by other web development projects would help

 

Thanks

Brian

_______________________________________________________

Juniper Bank

"Rated #1 in Customer Confidence"

Gomez Inc., Summer 2001 Internet Credit Card Scorecard

www.juniper.com

_______________________________________________________

This e-mail and any files transmitted with it may contain confidential and/or proprietary information. It is intended solely for the use of the individual or entity who is the intended recipient. Unauthorized use of this information is prohibited. If you have received this in error, please contact the sender by replying to this message and delete this material from any system it may be on.

_______________________________________________________

Juniper Bank

"Rated #1 in Customer Confidence"

Gomez Inc., Summer 2001 Internet Credit Card Scorecard

www.juniper.com

_______________________________________________________

This e-mail and any files transmitted with it may contain confidential and/or proprietary information. It is intended solely for the use of the individual or entity who is the intended recipient. Unauthorized use of this information is prohibited. If you have received this in error, please contact the sender by replying to this message and delete this material from any system it may be on.