No RTEMS 4.11 in RSB?

[Needell, Jerry]

Chris,
With regards to 4.11 being in a separate branch (and 4.9,4.10) heading that way, could you please clarify what that means.
How do I build 4.11 the tools (I assume it will be the same for 4.9.4.10 once branched). I am mostly concerned with building the tolls, not the RTEM kernels. I can get the kernel from git. It is the tool sets that I am am usually trying to recreate.

Thanks,
Jerry
> On May 14, 2016, at 5:26 PM, Chris Johns <chrisj at rtems.org> wrote:
> 
> On 13/05/2016 9:55 PM, Needell, Jerry wrote:
>> Chris,
>> That was all it took:
>> 4.10   and 4.9 build fine as long as 2 changes are made:
>> 
>> 1)
>> As Jan suggested:
>> delete the line
>> %include rtems-version.bset
>> from rtems/config/rtems-base.bset
> 
> I am not sure this is a good idea. Once we branch 4.9 and 4.10 the base version can be changed and this file works.
> 
>> 2)
>> as you suggested:
>> In config/tools/rtems-kernel-4.10.2.cfg oyu change:
>> %define rtems_kernel_version     4.10.2
>> to:
>> %define rsb_version 4.10.2
>> Note, the hash rtems_kernel_version also needs to change to rsb_version.
> 
> Yes this was needed.
> 
>> I made the same charge for 4.9 but I did not test it without the change - may not have mattered.
>> 
>> Note: for 4.9 it is also necessary to install texinfo-4.13 as described in the wiki.
>> 
>> 
>> But - change #1  now causes 4.12 to fail since items-version is not defined.
>> 
>> I’m trying to find a way to keep them all happy!
>> 
>> 
>> What  is the status of returning 4.11 to the RSB bsets list?
> 
> There is no plan to merge 4.11 back in and there are plans to remove 4.9 and 4.10 and to place them on their own branches just like 4.11. As you can see the ability to support all releases at the same time is complicated. Once 4.9 and 4.10 are split all that needs to change is 4.12 to 4.9 and 4.10 and things should work. Further to this all features in the one version can be confusing to users.
> 
> I need to tag and branch 4.9 and 4.10 and then make a tarball and add it to the FTP server.
> 
> Chris