I've done this once before where I moved the tag since the release was never publicly released.  However, you can argue that forks of mantisbt may use the old tag, however, they are not used for release MantisBT.

btw, I also updated the wiki page to address some of the points you highlighted and to update the process for updating the official and demo bugtrackers.

On Sun, Nov 11, 2012 at 2:35 PM, Damien Regad <damien.regad@merckgroup.com> wrote:
On 11.11.2012 19:01, Victor Boctor wrote:
> I've found a bug with anonymous access. I've checked in the fix.  I
> suggest we include this in 1.2.12.
> http://www.mantisbt.org/bugs/view.php?id=15200
> https://github.com/mantisbt/mantisbt/commit/d67c25724b409d79cdfe88f2381155b211eca277
> If you agree, please re-package and I'll publish.

Thanks for testing and fixing that issue, shame I (or anyone else)
didn't detect it before I completed preparation of the release. I agree
that it's serious enough to warrant its inclusion it in 1.2.12.

Now speaking of tagging and re-packaging, what should I do with the
'release-1.2.12' tag ? Update it ? In theory, once something's been
publicly released it shouldn't be changed... The alternative would be to
create a 'release-1.2.12a' tag. Please advise.


Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
mantisbt-dev mailing list