If we focus only on bugfixes and security then there is no concern
My coment was mostly related to new boards,drivers and architectures which
usually have spread comits
On Wed, 12 Feb 2025, 09:27 raiden00pl, wrote:
> Nathan, that's not what I mean.Look at this comment from Alin and
> discussio
Nathan, that's not what I mean.Look at this comment from Alin and discussion
below it: https://github.com/apache/nuttx/pull/15789#issuecomment-2648017787
wt., 11 lut 2025 o 21:33 Nathan Hartman
napisał(a):
> There will be regular releases as well and if I am understanding correctly,
> all PRs t
There will be regular releases as well and if I am understanding correctly,
all PRs that are accepted will go to a regular release, and in addition,
those that are important bugfixes or security will be backported to the LTS
release also. So it's not that PRs would be harder to accept, just that
we
I personally don't care about LTS releases and it seems to me that Nuttx
doesn't
have the resources for it. But if there are people willing to work on this
this,
I wish them good luck. What I don't like is the fact that the new PR
requirements
for LTS will make life as difficult as possible for con
I also think LTS point releases should focus on bugfixes and security only,
to ensure the maximum stability.
Nathan
On Tue, Feb 11, 2025 at 8:32 AM Sebastien Lorquet
wrote:
> Hello,
>
> I agree. Only bugfixes, criticity threshold to be determined, but new
> features seem unnecessary to me.
>
>
Hello,
I agree. Only bugfixes, criticity threshold to be determined, but new
features seem unnecessary to me.
Sebastien
On 11/02/2025 12:43, Tiago Medicci Serrano wrote:
Hi,
I would make the scope even more restricted. Considering an LTS should be
100% compatible with an existing defconfig
On Tue, Feb 11, 2025 at 9:55 AM Alin Jerpelea wrote:
> Hi all,
> there have been suggestions that we should create LTS releases
Lets see how our current code improvements work out in reality.. if
work as expected then there should be no need for LTS releases because
code should be self-compatible
Hi,
I would make the scope even more restricted. Considering an LTS should be
100% compatible with an existing defconfig, it should not add new drivers
and new HW. I propose it to contain only bugfixes and security patches.
Best regards,
Em ter., 11 de fev. de 2025 às 08:27, Alin Jerpelea
escre
I propose that for our first LTS we start with a small scope and we
backport only fixes, new hw and drivers
For the future releases we may consider expanding the scope if the workload
permits
What do you think ?
On Tue, Feb 11, 2025 at 10:55 AM Laczen JMS wrote:
> Hi Alin,
>
> I also encourage
Hi Alin,
I also encourage this. I would start by defining what is expected from a LTS:
A LTS release of NuttX is a release that will be maintained and
supported over a longer period of time (1 year).
LTS updates are mainly focused on bugfixes that where discovered and
corrected during the support
I propose that we start step by step
for our first LTS I aim to backport port the fixes for every quarter and
create a "." release in the same time we create normal releases
ex for 2025:
Match
13.0.0 LTS
Jun
13.0.1 LTS
13.1.0 regular
September
13.0.2 LTS
13.2.0 regular
December
13.0.3 LTS
13.3.0
Hello,
This is an excellent idea.
How will we manage maintenance of these LTS releases? Some fixes are
likely to require some backports?
Sebastien
On 11/02/2025 09:54, Alin Jerpelea wrote:
Hi all,
there have been suggestions that we should create LTS releases
I propose that we mark every
Hello Alin,
I would love to see this, as it would make maintaining our product much
easier.
Thanks for the proposal.
Michael
On Tue, Feb 11, 2025 at 9:55 AM Alin Jerpelea wrote:
> Hi all,
>
> there have been suggestions that we should create LTS releases
>
> I propose that we mark every Q1 (m
Hi all,
there have been suggestions that we should create LTS releases
I propose that we mark every Q1 (match) release as a LTS release and
maintain it for 2 years. this would always ensure a fresh LTS overlapping
the old one and allowing the users to migrate the code to the new release.
What do
14 matches
Mail list logo
