On Wed, May 21, 2025 at 10:59 AM Alin Jerpelea <jerpe...@gmail.com> wrote: > Hi Mateo, > I like the initiative but there are some things to consider > > On Tue, May 20, 2025 at 11:47 PM Tomek CEDRO <to...@cedro.info> wrote: > > On Tue, May 20, 2025 at 10:24 PM Matteo Golin <matteo.go...@gmail.com> > > wrote: > > > I took a look at the NuttX GitHub page, and now it seems that version > > updates (for instance, 12.9.0 recently) are > > > created as "tags" on GitHub (listed here > > https://github.com/apache/nuttx/tags), as opposed to "releases" (here > > there are > > > none https://github.com/apache/nuttx/releases). > > > > +1 for branch for each release +1 for releases with github releases > > (its done automatically when branch/tag is provided). That would put > > some better insight on project pace / development for newcomers and > > could attract new people :-) > > > > The question is if this is a big complication for Alin and if help > > here is needed? :-) > > > > > -1 our releases are signed and hosted on Apache servers. > I don't think that it is a god idea to have separate releases on github. > For each release we have the stabilization branch ex releases/12.9.0 which > contains all the code included in a release. > This branch can be used for generating release notes and will be updated > with security code for a security release
Hmm to be honest I also usually use GitHub releases for most projects.. and we can put signed artifacts from Apache servers on GitHub manually for NuttX releases even if the auto-release-automation is not used? I see that as project visibility increase too :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
