Chris Johns commented on a discussion: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/163#note_121036 I am sorry I do not know how the versioning on the docs site is handled. Anything thing we expose that references a released version should use the release tar ball. Anything on a branch is what is built. The branch builds, even a release branch, are not released and should not appear to be so. In regards to procedures I am interesting in what we have and how we are handling releases and for us a `VERSION` file in the source releases it. I am questioning the option and not the need for the documentation to vary. I am fine with small needed differences however I would find it concerning if the differences grew in size. I do not want a way for someone building the docs to make a version that appears to be released and I do not want the released docs sources to be used to build a development version. -- View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/163#note_121036 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
