[ANNOUNCE] Mir 0.1.9

[Daniel van Vugt]

Sure, not disastrous. Just that fixes documented (in the proposal) as 
being fixed in "0.1.9" may not actually have made it into the package. 
So inaccurate. It's nice to have accurate info about where things are 
fixed :)


On 02/05/14 14:46, Michał Sawicz wrote:
> On 02.05.2014 03:20, Daniel van Vugt wrote:
>> No problem. Next time we should be sure the proposal is top-approved
>> first. It wasn't top approved in this case so there was a real risk that
>> people like me could make further changes without knowing those changes
>> were too late to reach archive.
>
> FYI, it's actually safe in the sense that those changes would just not
> get into trunk. What gets pushed is a snapshot of trunk + branches being
> merged at the time of source package preparation.
>