Re: [rtems commit] cpukit: Add description of release version numbers

2022-01-28 Thread Sebastian Huber
On 28/01/2022 15:28, Christian MAUDERER wrote: So I think at the moment, the engineering manual is wrong. The release branch will always have the number N.0.0 as long as we don't change the release process. I think the manual is right and the version on the RTEMS 5 release branch is wrong. It

Re: [rtems commit] cpukit: Add description of release version numbers

2022-01-28 Thread Christian MAUDERER
Hello Sebastian, Am 28.01.22 um 14:16 schrieb Sebastian Huber: On 28/05/2021 08:25, Christian Mauderer wrote: Module:    rtems Branch:    master Commit:    023a27096223e33be1cdd3f8d2ccf11caeda72b1 Changeset: http://git.rtems.org/rtems/commit/?id=023a27096223e33be1cdd3f8d2ccf11caeda72b1 Aut

[PATCH] eng: Add rtems-central.git post branch procedures

2022-01-28 Thread Sebastian Huber
--- eng/release-process.rst | 26 ++ 1 file changed, 18 insertions(+), 8 deletions(-) diff --git a/eng/release-process.rst b/eng/release-process.rst index f6b2307..7c250ea 100644 --- a/eng/release-process.rst +++ b/eng/release-process.rst @@ -159,21 +159,23 @@ Release Repo

Re: Barrier Manager cross-node behaviour

2022-01-28 Thread Sebastian Huber
On 28/01/2022 14:39, Joel Sherrill wrote: On Fri, Jan 28, 2022, 7:15 AM Jerzy J wrote: Hi Joel, Thank you for your help and clarification, this is exactly what i needed! In terms of submitting this to the community, the situation is exactly as mentioned by Andrew. Thanks for the info Andre

Re: [rtems commit] cpukit: Add description of release version numbers

2022-01-28 Thread Sebastian Huber
On 28/05/2021 08:25, Christian Mauderer wrote: Module:rtems Branch:master Commit:023a27096223e33be1cdd3f8d2ccf11caeda72b1 Changeset: http://git.rtems.org/rtems/commit/?id=023a27096223e33be1cdd3f8d2ccf11caeda72b1 Author:Christian Mauderer Date: Wed May 26 09:39:13 2021 +020