Laczen commented on PR #15732: URL: https://github.com/apache/nuttx/pull/15732#issuecomment-2639580599
> > please split arch and documentation in separate PR if we try to maintain LTS releases this is a requirement > > In this case, @jerpelea , It makes sense to keep them in the same PR (two separate commits) because the documentation is coupled with the current implementation, so backporting it would also be associated. Does it make sense? @jerpelea You have made this same requirement in the dev mailinglist. However it is not clear to me why this would be a requirement for LTS releases. I propose before making this requirement for PR's a github issue is created regarding LTS releases, what they are, how they will be used (e.g. only backport bugs) and what to expect from LTS releases (e.g. any defconfig created out of tree should remain valid, disallowing changes to Kconfig options). Once this is clear it should be possible to decide how PR's should align with these requirements. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
