Bumping this up. It seems like we need a plan to tackle going through the 613 closed PRs and summarizing (only merged ones need to be summarized). This would be easier with a team of people... anyone want to help?
One way we could do this is one group take bug fixes, and another take features, and then make a list for each. Then we put them together in a document. -adam On Mon, Mar 30, 2020 at 11:31 AM Adam Feuer <a...@starcat.io> wrote: > Here's a list of all closed PRs since 2019-11-16, the date of NuttX > release 8.2: > > > https://github.com/apache/incubator-nuttx/pulls?q=is%3Apr+is%3Aclosed+closed%3A%3E2019-11-16+ > > There are 613 closed PRs. This might be motivation to get back to doing > them every two months. :) > > -adam > > On Sun, Mar 29, 2020 at 2:07 PM Adam Feuer <a...@starcat.io> wrote: > >> Nathan, >> >> A quick Google search yielded Reno – tooling for managing release notes. >> >> Reno docs: >> https://docs.openstack.org/reno/latest/ >> >> Reno source code: >> https://github.com/openstack/reno >> >> It can use ReStructuredText (RST) and has Sphinx integration. Zephyr, >> Rust, Clang, Python, and others also use RST and Sphinx. >> >> -adam >> >> On Sun, Mar 29, 2020 at 1:48 PM Nathan Hartman <hartman.nat...@gmail.com> >> wrote: >> >>> On Sun, Mar 29, 2020 at 2:03 PM Gregory Nutt <spudan...@gmail.com> >>> wrote: >>> > The organization of the release notes is fine, it is just making the >>> > level of effort needed to produce them manageable. This begs for some >>> > kind of tooling. >>> >>> I wonder if there is some Free/Open Source tooling that already exists >>> (preferably something with a community and user base that already >>> exists around it) that we could adopt for this purpose. >>> >>> Can anyone recommend such a tool? >>> >>> Nathan >>> >> >> >> -- >> Adam Feuer <a...@starcat.io> >> > > > -- > Adam Feuer <a...@starcat.io> > -- Adam Feuer <a...@starcat.io>
