Chris Johns started a new discussion: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/163#note_120984 I think root of the problem is original labels used for the versions do not make a distinction between "this" release and "the" release. Maybe there needs to be a distinction in the labels used for "the" release when building unreleased docs verses building released docs and the related text updated. I think the documentation for the release should be explicit about the released version and only reference it no matter what the state of source being built. I prefer only one way to make released things and I prefer we try to stay consistent with the way other packages manage releases verses development states. The docs are released when there is a `VERSION` file in the top directory. There is code to read and manage this file in `common/version.py`. If the docs are released "this" release labels (what we have) and "the" release labels (added) are the same. -- View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/163#note_120984 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
