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 >
