Am Mon, 11 Feb 2013 07:03:07 +0100 schrieb "deadalnix" <deadal...@gmail.com>:
> It seemed fixed in previous state of master, so either the tag is > wrong or we have a regression. What is the state of 2.062-b1 ? The tag is still pointing to the wrong commit, somehow updating it didn't work. Maybe we should just do this release as usual. After this release has been made we could discuss a release schedule first so that we now when 2.063 will be released. And then we can make a clear plan on how to switch to the new process.
