Re: Create Release Candidate GitHub Workflow

Svn url for review: https://dist.apache.org/repos/dist/dev/manifoldcf/apache-manifoldcf-2.26 Our area in this svn: https://dist.apache.org/repos/dist/dev/manifoldcf Our area for releases in this svn:

Re: Create Release Candidate GitHub Workflow

The script as it exists now (release.bat) creates the release artifacts, signs them, and copies them into the svn development area. To actually release, you then just need to move them (using svn move) to the release part of the area. The machine I used to do this on died but the svn URL for the

Re: Create Release Candidate GitHub Workflow

The open points now are related to the last two steps of our workflow: - Generating the file hashes using a shared GPG secret (in progress...) - Updating SVN public folders for publishing releases (TODO) We should agree with the Automated Release Process before proceeding:

Re: Create Release Candidate GitHub Workflow

Well we obviously need something that works, and just updating the script to use github commands is one way to do that and would generate releases like we do now. On Tue, Mar 12, 2024 at 9:00 AM Piergiorgio Lucidi wrote: > Hi Karl, > > I tried to look at the current process but It's not clear

Re: Create Release Candidate GitHub Workflow

Hi folks, now this workflow works correctly, you can take a look at the run log here: https://github.com/apache/manifoldcf/actions/runs/8437275847 You can see the new RC created as a tag in Github: https://github.com/apache/manifoldcf/releases/tag/2.27-RC0 There are some deprecated instructions

Re: Create Release Candidate GitHub Workflow

Hi Karl, I tried to look at the current process but It's not clear to me what I should do now. Should I just use svn commands from GitHub in order to execute the same steps? Or do we have an alternative way without using svn? Do you know if we have something GitHub-centric for managing releases?

Re: Create Release Candidate GitHub Workflow

Very good! In the past we've often had to add new commits to the release branch and create a new RC. The RCs have to be copied into the staging area (in an svn repo) and then when actually released there's a simple svn command to do that. Are you familiar with that process? For this reason it

Create Release Candidate GitHub Workflow

Hi folks, I have just pushed a potential GitHub workflow for creating the release candidate branch and artifacts [1]. The related issue is available in JIRA [2]. We need to test it but I think that it could be something close to what we need: 1. Create the new branch 2. Update CHANGES.txt,