We can assign issues/PRs to the next release milestone to track things we don't want to leave out in next release. We should categorize outstanding bugs to be included.
In my case I would like to include the build fix I have in PRs, for example. Another thing I'm thinking on is having the documentation support not only latest (master) but also stable (release). But I think this would not be a blocker. Best, Matias On Sun, Sep 13, 2020, at 10:55, Nathan Hartman wrote: > Hi folks, > > There have been many big changes since the last release including work > focused on reducing memory footprint, a major overhaul of the > documentation, and countless other things. > > We should get the next release started sometime soon. Is there anything in > particular that we should wait on before proceeding? > > Cheers, > Nathan >
