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 importance of all this and that we ultimately need to clear all licensing issues but this can't stop us from making a release right now. (For anyone interested in this Adam created a wiki page: https://cwiki.apache.org/confluence/display/NUTTX/License+Clearing) 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 Nathan in a different thread) 1. a) Create a release branch and keep accepting new features in master. Bugfixes that should be in the release are backported from master. _or_ b) Freeze the repos, accept only critical bugfixes, new features would wait for the next merging window. The release branches and tags should follow a well defined naming convention. The current convention is: nuttx-major.minor (ex. nuttx-8.3) The release candidate branches or tags should append -rcX at the end with X being the candidate iteration. 2. After review and testing, create release candidate tarballs. 3. Start soak period (we need to determine how long the soak period should be) to give downstream time to find/report/fix bugs. 4. If necessary, backport bug fixes and issue another release candidate. 5. When no more showstopper issues remain, create the final release tarballs. 2. The release date: Sooner rather than later. Please share your thoughts on what should be in the release process. We will create a wiki page for that for future references. There are some extra ASF steps that we will deal with once we get the above sorted out.
