# I'm moving the discussion to rqt ML.
Coming right to the point first, I have to admit that I didn't test
enough the latest patch  that was commited 3 days before my latest
release, and understand the issue caused by that  is critical for
certain users. While we try to fix this, should we rollback to the
status before  and release? What's the best solution here?
I apologize first, and I'll be more cautious for the future release.
Inline from here,
On Tue, Apr 2, 2013 at 8:00 AM, Dirk Thomas <dth...@osrfoundation.org
> Why did you released the packages twice - between both versions was not a single change?
I did release twice almost by accident. I don't exactly remember why I
had to do so, but it was because I had a problem in releasing due to
my familliarity with bloom at that time.
> Also was the release really necessary?
> In this case the latest changes are responsible for a regression.
> It definitely needs more testing after patches are being applied.
> Due to the very short time between the changes from Dorian and the release
> the issue was not found before.
> But now the problem is released and also synced to Groovy and Hydro.
Yes the release was necessary to apply a patch that was commited
almost 2 months ago. But again I should have tested the all commits
applied since last release.