AccuRev - promoting quicker projects past larger ones

Question

I feel like I'm experiencing a common problem, but I wasn't able to find anyone asking about it.

As the title indicates, we're forced to use AccuRev for SCM. We have our development stream under our QA stream. Let's say we're working on a big project that will be in QA for weeks before being released (we're following a scrum strategy). In the meantime, there's a bug fix that needs to go out before this big project. The problem is the bug fix affects some of the same files the big project uses. How would I get my files from development to production, without bringing the big project with me?

Sorry, I hope that makes sense! Thanks!

Answer 1

I think I found a solution that will work for us.

I plan on creating a snapshot off of the development stream after each successful deployment to production. Bug fixes/smaller projects will work off of this snapshot. That way I can keep anything I'm currently working on in DEV from getting inherited into my bug fix. When I'm ready to deploy my bug fix, I'll create another snapshot and re-parent my big project there. Then I'll revert the change package in QA and development, re-parent my bug fix to development, and promote as normal. It's a slightly modified version of what's explained in this article: https://accurev.wordpress.com/2008/03/27/pattern-for-stable-development/

Answer 2

If you are using the change package feature in AccuRev, you can select that issue and just promote those changes into the production stream.

Otherwise, you will need to determine the promote transaction(s) of the of the bug you fixed in development and change palette those fixes into production.