Thanks PJ for doing the switch. I was away for a few days, but took a look now and it seems to work fine.
Anything that needs doing for the move where you could use some help? Regards... Dominik. On Mon, Jul 7, 2025 at 12:46 PM PJ Fanning <fannin...@apache.org> wrote: > I also forgot to mention that our builds on the ASF CI machine use svn > checkouts so they will need to change too. > We have a GitHub CI job so checks the POI compilation so we are unlikely > to seriously bust the POI build but please be a bit careful until we can > get all the CI jobs building from the git repo. > > https://ci-builds.apache.org/job/POI/ > > On 2025/07/07 10:42:56 PJ Fanning wrote: > > The git repo is now our main repo. The svn repo is now read-only. > > The code freeze is over. > > Easiest to check out https://github.com/apache/poi > > > > Our docs need to be updated to reference the git repo instead of svn. > I'll look at this over the next few days. > > > > The docs could be an issue for a while as the poi-site svn has not been > moved nor has the symlink. > > Working Copy Root Path: $POI_HOME/src/documentation > > URL: https://svn.apache.org/repos/asf/poi/site/src/documentation > > > > I'm going to propose that we just move the files to src/documentation in > https://github.com/apache/poi (no symlink). > > > > I can set up a new branch in apache/poi to publish the poi.apache.org > website. The website would refresh when that branch is updated. `asf-site` > is the usual branch name in ASF repos. > > > > This is controlled by the `.asf.yaml` file that is in the root of our > code. > > > https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Introduction > > > > If there are no objections, I can look into getting the website > publishing working from our git repo in a few days. > > > > > > On 2025/06/17 13:58:45 Axel Howind wrote: > > > Not on Mac anymore unless you want to install or already have > homebrew, macports, or Fink. Xcode does not come with SVN anymore. There > are some commercial versions available though that also include cli tools > (and when I last checked had licensing terms for the free versions that I > could not agree with). > > > > > > But the main advantage of using git imho is the support for pull > requests and code reviews. I think the entry for possible new contributors > is also easier with a tool most developers are already familiar with. > > > > > > > Am 17.06.2025 um 11:02 schrieb stanton fisque <sfis...@gmail.com>: > > > > > > > > TBH svn clients are easy to get. > > > > > > > > but that's not a good reason to stick with svn. a move to git would > probably revitalize the ci/cd pipeline for this project. the only real > problem i see, is who wants to spend the effort to move the repo history > over. > > > > > > > > > > > > Stanton Fisque > > > > principal technologist > > > > latticeware.com > > > > portland, oregon > > > > > > > >> On Jun 16, 2025, at 19:36 PM, Axel Howind <a...@dua3.com> wrote: > > > >> > > > >> Definitely move to GitHub and not create another workaround > workflow to keep SVN alive. Tools drop SVN support (I think most already > have), and just getting a working SVN client is not as easy as it should be > (probably depends on platform). > > > >> > > > >>>> Am 17.06.2025 um 02:47 schrieb PJ Fanning <fannin...@apache.org>: > > > >>> > > > >>> I would support moving to git. > > > >>> GitHub CI has started working on our GitHub mirror. For ages, only > > > >>> commits to the trunk branch triggered jobs but now we are seeing > PRs > > > >>> lead to jobs triggering. > > > >>> Our main CI jobs are on https://ci-builds.apache.org/ though. > > > >>> > > > >>>> On Mon, 16 Jun 2025 at 20:11, Dave Fisher <w...@apache.org> > wrote: > > > >>>> > > > >>>> Hi Devs, > > > >>>> > > > >>>> Over the weekend I saw PJ was triaging some PRs from a > contributor, and thought I would take a look at some of the older ones and > do some triage. Because of the fact that GitHub.com/apache/poi is git > mirror of svn I was unable to close these PRs. I can close these issues > from a svn commit message: > > > >>>> > > > >>>> svn ci -m ‘closes #123, closes #345’ > > > >>>> > > > >>>> Here’s the GH docs about the commit message: > https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword > > > >>>> > > > >>>> If there are no objections I’ll create a file called > `.svn-gh-pr-closer`, append notes, and commit messages. > > > >>>> > > > >>>> The alternative would be to migrate over to GitHub. One > prospective way to start would be to add CI workflows to GH. > > > >>>> > > > >>>> Best, > > > >>>> Dave > > > >>>> > --------------------------------------------------------------------- > > > >>>> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org > > > >>>> For additional commands, e-mail: dev-h...@poi.apache.org > > > >>>> > > > >>> > > > >>> > --------------------------------------------------------------------- > > > >>> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org > > > >>> For additional commands, e-mail: dev-h...@poi.apache.org > > > >>> > > > >> > > > >> > --------------------------------------------------------------------- > > > >> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org > > > >> For additional commands, e-mail: dev-h...@poi.apache.org > > > >> > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org > > > For additional commands, e-mail: dev-h...@poi.apache.org > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org > > For additional commands, e-mail: dev-h...@poi.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org > For additional commands, e-mail: dev-h...@poi.apache.org > >
