Phase out `git svn` support in Git for Windows

[dscho]

Due to persistent maintenance challenges and the community's limited engagement and usage, git svn support in Git for Windows will be phased out over the next few releases.

Depending how much feedback this ticket sees, it might even be a good idea to drop support directly after v2.48.1.

[jrfnl]

Just a heads-up: I know of at least one big OSS project which is likely to see impact of this: WordPress. They still use SVN, so a lot of the committers commit via git svn.

Note: that this includes plugin/theme authors who need to update their plugin/theme in the wp.org repository...

[dscho]

Just a heads-up: I know of at least one big OSS project which is likely to see impact of this: WordPress. They still use SVN, so a lot of the committers commit via git svn.

Note: that this includes plugin/theme authors who need to update their plugin/theme in the wp.org repository...

@jrfnl thanks for the heads-up. Two questions:

• Are there any WordPress contributors who use Windows computers to contribute?
• If there are any, would they not be better served by using MSYS2 (provided that we manage to move Git for Windows so close to MSYS2 that git svn is properly supported there) or by using the Windows Subsystem for Linux?

I am asking because git svn support is really quite a maintenance burden, and I have seen very little assistance, if that, from the community that seems to require it.

[jrfnl]

@dscho I know for sure there are Windows users amongst that group, but I don't have access to numbers, let alone know the workflows used by people in that group.

Just wanted to raise awareness of potential fall-out.

As a fellow maintainer, I fully understand if you still go ahead if the maintenance burden is that high.

[dscho]

/add relnote blurb Due to persistent maintenance challenges and the community's limited engagement and usage, git svn support in Git for Windows will be phased out over the next few months.

The workflow run was started