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: https://issues.apache.org/jira/browse/INFRA-25665?focusedCommentId=17832209&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17832209 Practically INFRA will generate a new GPG key and they will add the public key into the ManifoldCF KEYS file. This will let us manage the generation of file hashes using a GitHub actions. Do you all agree with this? Please let me know. Thanks. Cheers, PG Il giorno mar 26 mar 2024 alle ore 17:19 Karl Wright <daddy...@gmail.com> ha scritto: > 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 <piergior...@apache.org > > > wrote: > > > 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
