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

2022-01-30 Thread Chris Johns
On 29/1/22 2:36 am, Sebastian Huber wrote: > 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

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.

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

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