Hi JB,
Greetings to Mexico! I was using Infra's "SVN to Git migration"
service desk. That seems like a standard way for migration to me. It
has also worked fine in the past.
Could you explain the role of the SCM-Publish Maven plugin? What would
be different from just committing the changes of the
I agree and it's what we have: the website sources are on my github and we will
move it on apache git. Anyway the source is not where you promote with the
scm-publish. The PR or patches are not created based on the "resulting"
location (on svn now) but on the sources (on my github now). Th
Hu
OK it makes sense then even if I don't see any value (svn or git will use
scm-publish maven plugin).
The jira looks weird to me as Max asked to populate the git with svn: we can
start with empty git and publish with the plugin.
RegardsJB
Sent from my Samsung device
Original
Hi JB,
ASF infra now offer Git pubsub to support website source code [1]
I think this is what Max was trying to enable so instead of using svn for
website it will be using Git that also allow pubsub to publish it.
- Henry
[1] https://blogs.apache.org/infra/entry/git_based_websites_available
On
Hi guys
Max your jira doesn't make sense imho: the svn for the website is for pubsub,
it's not where the website source has to be located. The website can be on git
or where ever you want but the scm-publish has to be on svn.
Please close your jira and wait when I'm back to deal with that.
Alright, I've asked the Infra team to migrate the repository to Git
and setup a GitHub sync.
Git migration:
https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-11318
GitHub sync:
https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-11319
Cheers,
Max
On Wed, Feb 24,
