We've already agreed on the version numbering. It's pretty much the same as it was + the patch number. So if there is incompatible change to the APIs, we need to bump the major number to 10.
> wouldn't you like to create a milestone for next version as well? We used Github Project last time to track PRs and triage them for the release notes. I'm not sure how Milestones would work here. We can give a shot if you have a clear vision. Can we use both Project and Milestones, they don't seem to be mutually exclusive. On Fri, Aug 14, 2020 at 8:54 PM Nathan Hartman <hartman.nat...@gmail.com> wrote: > > On Fri, Aug 14, 2020 at 2:51 PM Gregory Nutt <spudan...@gmail.com> wrote: > > > > > > Nathan started this here: > > > https://cwiki.apache.org/confluence/display/NUTTX/NuttX+9.2 > > > > > > I would say let's fill that out, we can change it to 10.0 later. I > > > will kick off getting the tracking board and the PR changes going in > > > next week, that I thought worked quite well for realtime and async > > > collaboration last time. > > Done > > > Thanks for documenting the wdog changes. My computer blew up recently and I > was stuck with only mobile for a week so I've been playing catch-up... > > In terms of how to do our version numbering, ASF doesn't dictate any > policies about that AFAIK. Those sorts of technical decisions are left up > to the individual projects. I agree with semantic versioning and I think we > should bump the major version number to 10 given the recent breaking > changes to APIs. > > Nathan
