On 25/1/22 5:37 pm, Sebastian Huber wrote: > On 25/01/2022 01:09, Chris Johns wrote: >> On 25/1/22 1:39 am, Sebastian Huber wrote: >>> how do we want to proceed with the integration of the new validation test >>> suite? >>> At the moment it is not clear to me what issues are left to resolve and >>> what I >>> can do to address them? >> >> I believe I have been clear about what I see as being needed: >> >> https://lists.rtems.org/pipermail/devel/2022-January/070323.html > > Sorry, I don't know what I have to do next.
Sure and I am sorry if this was not clear. > The release process for rtems-central is quite clear from my point of view. I would not have raised this if I was in the same position. You are the only person I know who understand rtems-central. I only have an overview of it and I I am sorry but I have no spare time in invest in learning more about it. I do have the responsibility of releasing RTEMS and if I accept these changes without any of the needed support in place history has taught me I am left to provide it. Tools and scripts that shows how a process is to work would go a long long way to resolving this issue. The RTEMS Release repo is a series of FreeBSD scripts I use to release ... https://git.rtems.org/rtems-release/ I have not touched it in a while and it needs work to change it to support waf. > We just have to create a > release branch for RTEMS 6 and reference release branch commits in the > submodules. How do you validate the generated sources in the sub-modules match those in the branched submodules? I think this should be done as part of the release procedure to catch any mistakes. Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
