Chris Johns commented on a discussion on eng/release-process.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/62#note_113559 > > #. Verify the release has been uploaded by checking the link: > > - https://ftp.rtems.org/pub/rtems/releases/<VERSION>/<VERSION>.<REVISION> > - > -#. Tag the release repositories with the following command: > + ``https://ftp.rtems.org/pub/rtems/releases/<VERSION>/<VERSION>`` > Yes. There is a separation of the administrator related functions and the release process and the responsibilities of the release manager. The admin side is a work in progress and I can fill both roles but we need to move to a more formal approach. The perms are set so only @amar and I myself have access. I have done this to minimize possible mistakes as `dispatch@` access lets the user see the ftp files and to enforce once a release is public no one can touch the released file tree. -- View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/62#note_113559 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
