Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add RELEASE-PROCESS.md #1435

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add RELEASE-PROCESS.md #1435

wants to merge 1 commit into from

Conversation

ac000
Copy link
Member

@ac000 ac000 commented Sep 18, 2024

The document describes the release process for NGINX Unit.

@ac000 ac000 force-pushed the release branch 8 times, most recently from 8f6f68e to 1637ab2 Compare September 23, 2024 12:42
@ac000 ac000 marked this pull request as ready for review September 23, 2024 12:47
The document describes the release process for NGINX Unit.

Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
@ac000
Copy link
Member Author

ac000 commented Sep 25, 2024

Add a section to check for the new release on GH.

$ git range-diff 1637ab23...10100df1
1:  1637ab23 ! 1:  10100df1 Add RELEASE-PROCESS.md
    @@ RELEASE-PROCESS.md (new)
     +    $ git push <upstream> 1.33.0
     +
     +
    ++# A new 'Release'
    ++
    ++After a while the new release should show up at
    ++<https://github.com/nginx/unit/releases>
    ++
    ++
     +# Tarball
     +
     +We need to publish an archive of the source and a checksum.

@avahahn
Copy link
Contributor

avahahn commented Oct 7, 2024

Note:

We also need a section to update these example dockerfiles in the docs repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants