why not?
# announceh
hundreds-breakfast-49010
11/06/2020, 5:47 PMwhy not?
h
hundreds-father-404
11/06/2020, 5:50 PMOnly reason I can think is that 2.0 was last week, and we normally go about 3-4 weeks for each new release. But I think this was an unusual thing with 2.0
f
fast-nail-55400
11/06/2020, 5:51 PMI would give the 2.0.0 news some time to “settle” in the public’s mind
fast-nail-55400
11/06/2020, 5:52 PMI also wouldn’t worry about 2.1.0.dev0 having more changes than a regular dev0 release
fast-nail-55400
11/06/2020, 5:52 PMwith time-based releases, the changes that make it made it in
h
hundreds-father-404
11/06/2020, 5:52 PMI think my bigger motivation is the blog about Py3 migrations. We wanted the blog next week, but I don’t want to be talking about features not in a stable release
w
witty-crayon-22786
11/06/2020, 5:53 PMit’s 3-4 weeks of time on master
witty-crayon-22786
11/06/2020, 5:53 PMnot between the stable releases, per-se
👍 1
witty-crayon-22786
11/06/2020, 5:53 PMso the clock started when the 2.0.x branch was cut
witty-crayon-22786
11/06/2020, 5:56 PM…which was oct 11th