@@ -18,9 +18,10 @@ We are planning to release a stable 0.4.4 release on 15 September. That's the d
There are still some 044-must/044-should issues that
I think we have several possible choices here:
* If there are no further risky changes in 0.4.4 between now and 15 September, we can just release 0.4.4 stable on that date.
* If we want to do futher risky changes between now and 15 September, it would probably be okay to plan for another release candidate on 1 September. That would let me put out a stable when I get back.
* If ou don't do a release candidate between now and when I get back, but there _are_ risky changes, then we should put out a release candidate when I'm back, and we can plan to put out the stable 2-3 weeks after that.
* If there are no further risky changes in 0.4.4 between now and 15 September, we can just release 0.4.4 stable on that date.
* If we want to do futher risky changes between now and 15 September, it would probably be okay to plan for another release candidate on 1 September. That would let me put out a stable when I get back.
* If you don't do a release candidate between now and when I get back, but there _are_ risky changes, then we should put out a release candidate when I'm back, and we can plan to put out the stable 2-3 weeks after that.
I have updated the ReleasingTor.md documentation in the master branch to reflect current practice.
