Community
Participate
Working Groups
I20040506 The new versions of the releng tool forces the tag and commit steps to be together in the wizard. If committing fails because someone else already touched a map file I have to restart from the beginning (right?). Retagging does no harm but it takes quite long on low bandwith connections (we tag 28 projects). The older version only tagged and updated the local map files. I could then manually merge if there were conflicts when releasing the map files.
You do not need to start from scratch. By the time you get to the commit, eveything has been done except the commit. All you should need to do is resolve the conflicts in the map file and commit it. You do not need to rerun the release.
Well, well - I have to leave the wizard and do it outside the wizard directly on the map file, right. However, since the tool now tries to bind these together it should also be able to handle such a case in some way, e.g. 1. compare 2. tag 3. commit 4. show merge dialog in case of conflicts Note: I was happy with the old version which simply updated my local map files. This was a clear workflow.
When time presents itself, I will look into providing options to support the old workflow in the new wizard.
A a checkbox which allows me to always do the committing outside would also be OK.
That's what I had in mind (as well as a fix for bug 61620)
I'm going to close this bug, I assume it doesn't apply anymore.
(In reply to comment #6) > I'm going to close this bug, I assume it doesn't apply anymore. Yes it still does. The tool still behaves as written in comment 0.
I'm going to close this as we don't use the releng tool anymore.
