Message201085
| Author |
tim.peters |
| Recipients |
Arfrever, asvetlov, bjornedstrom, christian.heimes, dstufft, englabenny, ezio.melotti, gregory.p.smith, haakon, habnabit, jcea, larry, maker, markk, pitrou, python-dev, sbt, tim.peters |
| Date |
2013年10月23日.23:40:34 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1382571634.42.0.339190161392.issue16113@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
@Larry, you seem to be misreading this. They're not saying 3.4 can't be released until this feature is added. It's _already_ been added. They're saying 3.4 possibly can't be released until this feature is _removed_ - but whether it needs to be removed is outside of our control, and is not yet known.
> "release blocker" means "the release cannot go out until this
> issue is solved"
Yes - and this issue has not been solved yet. It should indeed be solved before 3.4 is released, so "release blocker" is spot on. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年10月23日 23:40:34 | tim.peters | set | recipients:
+ tim.peters, gregory.p.smith, jcea, pitrou, larry, christian.heimes, habnabit, ezio.melotti, Arfrever, asvetlov, englabenny, maker, python-dev, sbt, bjornedstrom, dstufft, markk, haakon |
| 2013年10月23日 23:40:34 | tim.peters | set | messageid: <1382571634.42.0.339190161392.issue16113@psf.upfronthosting.co.za> |
| 2013年10月23日 23:40:34 | tim.peters | link | issue16113 messages |
| 2013年10月23日 23:40:34 | tim.peters | create |
|