Build failed in Jenkins: NuttX-Nightly-Build #80

See Changes: -- [...truncated 519.74 KB...] Cleaning... Configuring... Copy files Select CONFIG_HOST_LINUX=y Refreshing... Building NuttX... ---

Re: The Release

Hi, I would make a check list like so [1], this one assumes you are using the ordinary disclaimer. I’ve reviewed hundreds and hundreds of releases so can help out. I also know what the IPMC looks out for and I’m currently the VP of the Incubator. Thanks, Justin 1. https://cwiki.apache.org/co

Re: [DISCUSS] Release Notes

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

Re: [DISCUSS] Release Notes

On Sun, Mar 29, 2020 at 2:03 PM Gregory Nutt 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

Re: [DISCUSS] Release Notes

> Release notes are already pulled from the source code and placed on the > webpage with the release. > Awesome! -adam -- Adam Feuer

Re: [DISCUSS] Release Notes

On Sun, Mar 29, 2020 at 1:00 PM Adam Feuer wrote: > Having the release notes living apart from the software doesn't sound good > to me– they could get out of sync. We can have copy the release notes to a > web page manually or by a script if we need to. > Release notes are already pulled from th

Re: [DISCUSS] Release Notes

What I meant by the release notes want to live in source control is that that they are fixed to that point in the software version control repository. They can be updated later as necessary, but if someone needs to check out that version (to find a bug, for particular vendor support, etc.) the note

Re: [DISCUSS] Release Notes

On Sun, Mar 29, 2020 at 2:43 PM Gregory Nutt wrote: > > > The release notes really want to be in source control, > > That is the reason that I always kept the ReleaseNotes in the > repository. Then there is no possibility that the ReleaseNotes can ever > become decouple from the release even aft

Re: [DISCUSS] Release Notes

The release notes really want to be in source control, That is the reason that I always kept the ReleaseNotes in the repository.  Then there is no possibility that the ReleaseNotes can ever become decouple from the release even after years and changes in ISPs. That is the same reason that

Re: [DISCUSS] Release Notes

Hi, I put Nathan's outline into the NuttX Wiki here: https://cwiki.apache.org/confluence/display/NUTTX/NuttX+9.0 The release notes really want to be in source control, but maybe having the outline here would help– we could copy this to a text file once it's done. Wiki pages are great for getting

Re: The Release

Thank you Nathan for this detailed procedure. I think the date is reasonable. Even though personally I was hoping to have a release earlier. But given all the steps outlined, I find it reasonable. That's enough time to prepare and for contributors to get last-minute changes ready. Let's please get

Re: [DISCUSS] Release Notes

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 There is tools/logparser.c, but it was designed specifically to convert the git log into the format used in the ChangeLog.  It is usefu

Re: [DISCUSS] Release Notes

I think we need to keep the release notes, they help people understand why they would want to upgrade. Let's make them succinct, however. I like the list of major parts, maybe we can add "Boards" to "Architecture Support" and add another part for other subsystems like, crypto, graphics, net, f

Re: [DISCUSS] Release Notes

I think we need to keep the release notes, they help people understand why they would want to upgrade. Let's make them succinct, however. I like the list of major parts, maybe we can add "Boards" to "Architecture Support" and add another part for other subsystems like, crypto, graphics, net, file

[DISCUSS] Release Notes

Earlier, in the thread "The Release"... On Sun, Mar 29, 2020 at 11:44 AM Gregory Nutt wrote: > Do we plan to generate Release Notes? In my experience that is the most > difficult part of the release (the rest is fun). Abdelatif tells me that > there are 1051 commits. That is a much lower number

Re: The Release

On Sun, Mar 29, 2020 at 11:44 AM Gregory Nutt wrote: > Do we plan to generate Release Notes? In my experience that is the most > difficult part of the release (the rest is fun). Abdelatif tells me that > there are 1051 commits. That is a much lower number that I expecteded, > lower than most old

Re: The Release

My recommendations (pending input from the community of course) are: Do we plan to generate Release Notes?  In my experience that is the most difficult part of the release (the rest is fun). Abdelatif tells me that there are 1051 commits.  That is a much lower number that I expecteded, low

Re: The Release

On Sun, Mar 29, 2020 at 8:10 AM Abdelatif Guettouche wrote: > For this thread, I'd like if we can agree on (not only discuss) two > things: 1. The release process. 2. The date of the first Apache > release. > > 1. The release process: > Here is some of what has been suggested before. (Most by Nath

Re: The Release

On Sun, Mar 29, 2020 at 9:11 AM Nathan Hartman wrote: > Let's make a big push and make this happen!!! > I think we should bump the major version number, both to signify the change to ASF and because this release contains substantially more changes than previous ones. Nathan

Re: The Release

On Sun, Mar 29, 2020 at 8:10 AM Abdelatif Guettouche < abdelatif.guettou...@gmail.com> wrote: > Hi, > > It's almost 6 months since our last release, we didn't only miss one > release cycle, but we are approaching the third. It is safe to say > that we should consider this with some urgency. > > P

The Release

Hi, It's almost 6 months since our last release, we didn't only miss one release cycle, but we are approaching the third. It is safe to say that we should consider this with some urgency. Please let's not get caught in the discussion of licensing headers, ICLAs, SGAs, etc. I understand the impor