Re: [PATCH] Upgrade to 5.0.0

On 16/11/17 8:59 pm, Sebastian Huber wrote: > On 16/11/17 10:32, Chris Johns wrote: >>> In this manual: >>> >>> >>> |/bd/rtems/4.11.0/tools| >>>     Production prefix for RTEMS 4.11.0 compiler, debuggers and tools. >>> |/bd/rtems/4.11.0/bsps| >>>     Production prefix for RTEMS 4.11.0 Board Support

Re: [PATCH] Upgrade to 5.0.0

On 16/11/17 10:32, Chris Johns wrote: In this manual: |/bd/rtems/4.11.0/tools|    Production prefix for RTEMS 4.11.0 compiler, debuggers and tools. |/bd/rtems/4.11.0/bsps|    Production prefix for RTEMS 4.11.0 Board Support Packages (BSPs). What should be the content of "tools" and "bsps"?

Re: [PATCH] Upgrade to 5.0.0

On 16/11/17 8:18 pm, Sebastian Huber wrote: > On 15/11/17 22:13, Chris Johns wrote: >> On 13/11/2017 18:56, Sebastian Huber wrote: >>> There will be no 5.1.X release with X != 0. We have a version scheme change >>> and >>> not simply a major version number bump. I think is quite good explained in

Re: [PATCH] Upgrade to 5.0.0

On 15/11/17 22:13, Chris Johns wrote: On 13/11/2017 18:56, Sebastian Huber wrote: There will be no 5.1.X release with X != 0. We have a version scheme change and not simply a major version number bump. I think is quite good explained in the GCC development page how it works (Version Numbering Sc

Re: [PATCH] Upgrade to 5.0.0

On 13/11/2017 18:56, Sebastian Huber wrote: > There will be no 5.1.X release with X != 0. We have a version scheme change > and > not simply a major version number bump. I think is quite good explained in the > GCC development page how it works (Version Numbering Scheme for GCC 5 and Up): > > htt

Re: [PATCH] Upgrade to 5.0.0

On 11/11/17 22:58, Chris Johns wrote: On 11/11/17 7:40 pm, Sebastian Huber wrote: - Am 11. Nov 2017 um 5:06 schrieb Chris Johns chr...@rtems.org: On 10/11/2017 17:30, Sebastian Huber wrote: On 09/11/17 23:52, Joel Sherrill wrote: My question about the version number went unanswered. Is th

Re: [PATCH] Upgrade to 5.0.0

On 11/11/17 7:40 pm, Sebastian Huber wrote: > - Am 11. Nov 2017 um 5:06 schrieb Chris Johns chr...@rtems.org: >> On 10/11/2017 17:30, Sebastian Huber wrote: >>> On 09/11/17 23:52, Joel Sherrill wrote: My question about the version number went unanswered. Is this the point were we are

Re: [PATCH] Upgrade to 5.0.0

- Am 11. Nov 2017 um 5:06 schrieb Chris Johns chr...@rtems.org: > On 10/11/2017 17:30, Sebastian Huber wrote: >> On 09/11/17 23:52, Joel Sherrill wrote: >>> My question about the version number went unanswered. Is this the point >>> were we are switching to two digit versions? This thread has

Re: [PATCH] Upgrade to 5.0.0

On 10/11/2017 17:30, Sebastian Huber wrote: > On 09/11/17 23:52, Joel Sherrill wrote: >> My question about the version number went unanswered. Is this the point >> were we are switching to two digit versions? This thread has 5.0.0 in the >> title (3 digits, no change in style) but the current tool

Re: [PATCH] Upgrade to 5.0.0

On 10/11/2017 20:16, Sebastian Huber wrote: > On 09/11/17 23:47, Chris Johns wrote: >> On 09/11/2017 17:24, Sebastian Huber wrote: 2. Documentation website repo. Easy. >>> I don't know how to do this. >>> >> https://git.rtems.org/chrisj/rtems-admin.git/ >> > > Ok, should I do this? > Yes if

Re: [PATCH] Upgrade to 5.0.0

On 09/11/17 23:47, Chris Johns wrote: On 09/11/2017 17:24, Sebastian Huber wrote: 2. Documentation website repo. Easy. I don't know how to do this. https://git.rtems.org/chrisj/rtems-admin.git/ Ok, should I do this? -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-8217

Re: [PATCH] Upgrade to 5.0.0

On 09/11/17 23:52, Joel Sherrill wrote: My question about the version number went unanswered. Is this the point were we are switching to two digit versions? This thread has 5.0.0 in the title (3 digits, no change in style)  but the current tools are "*-rtems5" which implies two digit release nu

Re: [PATCH] Upgrade to 5.0.0

On Thu, Nov 9, 2017 at 4:58 PM, Chris Johns wrote: > On 10/11/2017 03:45, Joel Sherrill wrote: > > > > Just to be clear, we won't have a 5.0.0 release, will we? Are we also > going to > > the two digit release numbers? > > No. The wiki page had 'minor release dot number' which was not that clear

Re: [PATCH] Upgrade to 5.0.0

On 10/11/2017 03:45, Joel Sherrill wrote: > > Just to be clear, we won't have a 5.0.0 release, will we? Are we also going > to > the two digit release numbers? No. The wiki page had 'minor release dot number' which was not that clear. I have updated the page to have 'version dot release number'

Re: [PATCH] Upgrade to 5.0.0

On Thu, Nov 9, 2017 at 4:47 PM, Chris Johns wrote: > On 09/11/2017 17:24, Sebastian Huber wrote: > >> 2. Documentation website repo. Easy. > > > > I don't know how to do this. > > > > https://git.rtems.org/chrisj/rtems-admin.git/ > > >> 3. Release procedure repo. Easy. > > > > Do we really need a

Re: [PATCH] Upgrade to 5.0.0

On 09/11/2017 17:24, Sebastian Huber wrote: >> 2. Documentation website repo. Easy. > > I don't know how to do this. > https://git.rtems.org/chrisj/rtems-admin.git/ >> 3. Release procedure repo. Easy. > > Do we really need another repo? Could we please place this to the tools or > RTEMS. >

Re: [PATCH] Upgrade to 5.0.0

On Thu, Nov 9, 2017 at 8:01 AM, Sebastian Huber wrote: > On 09/11/17 14:58, Joel Sherrill wrote: > >> >> 5. Trac wiki. Medium(?). A wiki search of 4.12 gives 21 hits. >> >> >> This is probably the most important area to fix: >> >> https://devel.rtems.org/wiki/Release >>

Re: [PATCH] Upgrade to 5.0.0

On 09/11/17 14:58, Joel Sherrill wrote: 5. Trac wiki. Medium(?). A wiki search of 4.12 gives 21 hits. This is probably the most important area to fix: https://devel.rtems.org/wiki/Release I will do this today. 6. rtems.

Re: [PATCH] Upgrade to 5.0.0

On Nov 9, 2017 12:24 AM, "Sebastian Huber" < sebastian.hu...@embedded-brains.de> wrote: On 09/11/17 05:58, Chris Johns wrote: > On 08/11/2017 23:29, Sebastian Huber wrote: > >> I can build RTEMS with the updated RTEMS tools and RSB (patches sent >> today). I >> plan to commit this tomorrow. With

Re: [PATCH] Upgrade to 5.0.0

I updated everything that I know of and I have permission to change. Open is: https://devel.rtems.org/ticket/3220 5. Documentation website repo. Easy. 6. Release procedure repo. Easy. 9.rtems.org website. That needs Joel. 10. Make announcement on the devel and user mailing list Something el

Re: [PATCH] Upgrade to 5.0.0

On 09/11/17 05:58, Chris Johns wrote: On 08/11/2017 23:29, Sebastian Huber wrote: I can build RTEMS with the updated RTEMS tools and RSB (patches sent today). I plan to commit this tomorrow. With respect to the documentation of the release process please see also: https://lists.rtems.org/piperm

Re: [PATCH] Upgrade to 5.0.0

On 08/11/2017 23:29, Sebastian Huber wrote: > I can build RTEMS with the updated RTEMS tools and RSB (patches sent today). I > plan to commit this tomorrow. With respect to the documentation of the release > process please see also: > > https://lists.rtems.org/pipermail/devel/2017-November/019400.

Re: [PATCH] Upgrade to 5.0.0

I can build RTEMS with the updated RTEMS tools and RSB (patches sent today). I plan to commit this tomorrow. With respect to the documentation of the release process please see also: https://lists.rtems.org/pipermail/devel/2017-November/019400.html -- Sebastian Huber, embedded brains GmbH Add

Re: [PATCH] Upgrade to 5.0.0

On 18/10/2017 18:47, Chris Johns wrote: > On 18/10/17 4:07 pm, Sebastian Huber wrote: >> Could we please move this content from the wiki into a Git repository? Do we >> really need a separate repository for this release stuff? Could we move this >> into the RTEMS repository as a replacement for the

Re: [PATCH] Upgrade to 5.0.0

On 18/10/17 4:07 pm, Sebastian Huber wrote: > On 17/10/17 21:34, Chris Johns wrote: >> On 17/10/17 4:44 am, Sebastian Huber wrote: >>> Tool name will be "rtems5", e.g. arm-rtems5-gcc. >> Why not rtems5.0 and then rtems5.1? > > We don't have different tool versions for bugfix releases, e.g there ar

Re: [PATCH] Upgrade to 5.0.0

On 17/10/17 21:34, Chris Johns wrote: On 17/10/17 4:44 am, Sebastian Huber wrote: Tool name will be "rtems5", e.g. arm-rtems5-gcc. Why not rtems5.0 and then rtems5.1? We don't have different tool versions for bugfix releases, e.g there are no 4.11.0, 4.11.1, 4.11.2, ... tools. It is just 4.1

Re: [PATCH] Upgrade to 5.0.0

On 17/10/17 4:44 am, Sebastian Huber wrote: > Tool name will be "rtems5", e.g. arm-rtems5-gcc. Why not rtems5.0 and then rtems5.1? Do we have the tool naming written up any where? > Next release will 5.1.0. Branch version after release will be 5.1.1. > Next master will be 6.0.0. I have added a