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 used by the upload-release-artifact action that should be replaced with something different. Probably I should use the hub command to simplify everything. I only need to upload the RC artifacts in SVN and I think that the tricky part is done :-P What do you think? Please let me know. Cheers, PG Il giorno mar 12 mar 2024 alle ore 13:59 Piergiorgio Lucidi < piergior...@apache.org> ha scritto: > 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? > > Cheers, > PG > > Il giorno mar 5 mar 2024 alle ore 21:53 Karl Wright <daddy...@gmail.com> > ha scritto: > >> 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 may be >> better to separate the creation of the release branch from everything >> else. >> >> Karl >> >> >> On Tue, Mar 5, 2024 at 9:23 AM Piergiorgio Lucidi <piergior...@apache.org >> > >> wrote: >> >> > 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, build.xml and all the poms >> > 3. Run the Ant build >> > 4. Run the Maven build (if we want to push artifacts on public repos) >> > 5. Check licenses using Apache RAT >> > 6. Commit and push the new branch >> > 7. Upload artifacts as GitHub release assets >> > >> > Any feedback? >> > Thanks everyone. >> > >> > Cheers, >> > PG >> > >> > [1] - >> > >> > >> https://github.com/apache/manifoldcf/blob/CONNECTORS-1754/.github/workflows/create-release-candidate.yml >> > >> > [2] - https://issues.apache.org/jira/browse/CONNECTORS-1754 >> > -- >> > Piergiorgio >> > >> > > > -- > Piergiorgio > -- Piergiorgio
