Re: Update of release scripts to work with git / Github instead of Subversion

On 4/25/25 06:05, Graham Leggett via dev wrote:
> On 25 Apr 2025, at 11:07, Ruediger Pluem <[email protected]> wrote:
> 
>> I currently try to update our release scripts to work with git / Github instead of Subversion, but I get a little bit stuck.
>> The main reason I get stuck is the technical difference of tags between git and Subversion.
>> Currently we create release tags / candidates in Subversion which we use as small / short branches to which we commit a small
>> amount of changes e.g. the changes in include/ap_release.h. Once we have done this on the final candidate we never touch this
>> branch again. We consider it a tag now.
>> Doing the same with git would mean that we also would need to create branches for release candidates and then tag the final commit
>> on these branches appropriately. Renaming and removing of stale intermediate candidates would also work with git even though it is
>> not that straight forward as with Subversion. But in the end we would have a tag for each release plus a branch. This has the
>> potential to bloat our branches in git. Hence my question is if we want to continue this approach or if we want to use a different
>> approach. And if we want to keep this approach do we want to prefix the names of these release branches with e.g. 'release/'?
> 
> My first thought is how much of the ecosystem out there breaks by changing this. Distros rely on us doing things in a certain way to detect updates, etc.
> 
> Second is does this now rely on us having Github accounts? Github and Apache are separate organisations, and mixing them is not good.

Rely is perhaps too strong a word to use here, but not entirely 
inaccurate. You can continue using your ASF credentials and push to 
gitbox.apache.org the same way you'd push to svn right now, so 
commit-wise you're able to continue your work wherever the repository is.

For interacting with GitHub PRs and issues, you would need a GitHub 
account if you intend to comment on those...for now at least, there are 
some ideas in the pipeline for a way to reply to an issue or PR via 
email, but that's a while away. You can still close/merge issues and PRs 
using the commit title/body interface for that (things like "this fixes 
#123", even without a GitHub account.

> 
> Regards,
> Graham
> --
>