Hi Thomas, yes, I agree, but as always devils are in the details.
We may proceed like this: Start with an official vote to move to git (yes/no) in two or more repos, two or more repos for sites, a separate repo for automatically builds as javadoc, reports and maven structure or not? I am not sure, if all this generated content should go into the asf-site or build in an extra step. Could we still use our xdoc site building? Have we a choice? What amount of time will this take? End of the year? At the moment I think, we should have at least two publishing repos: turbine-site and (t)-fulcrum-site, which would publish to a sub project, but this is not exact, what we do now. Could our current structure mapped easily to the new mechanisms? I am not entirely sure. For site building a Jenkins build might be the easiest way to go as some template scripts exist with pysubhub mechanism, that is a build is triggered per commit. Should we get an interim repo, that is we could just do our svnpubsub web site publishing? I would say yes at the moment (and will give this answer to Gavin McDonald in the INFRA- ticket), as there a couple of questions and procedures not yet decided. If we migrate to git repos, we probably will use this option: - Management tools, last paragraph in https://infra.apache.org/project-site.html = https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features . There is also a sub project publishing mentioned. Any thoughts about this? Next steps IMO: 1. Activate interim svn solution again (INFRA) 2. Prepare a vote with above mentioned options (TURBINE DEV MAILING LIST) 3. Migrate repos (or not) + migrate site + site buillding (or not) .. Best regards, Georg Von: Thomas Vandahl <[email protected]> An: Turbine Developers List <[email protected]> Datum: 05.08.2021 15:48 Betreff: Re: Migrating from Apache CM/SVN to Git Hi Georg, > Am 05.08.2021 um 15:35 schrieb Georg Kallidis <[email protected]>: > > At the moment I think, we should just think to migrate our scm from SVN to > Gitbox, and might then use gitpubsub. For now anyone interested in this > topic please watch issue INFRA-22176 and comment here or there. This is probably the best idea - move everything to git. I remember that an infra ticket is required for every target repository. We could even use the opportunity to reorganize our repos a bit (separate repos for Fulcrum for sure, what about one repo per component?) Bye, Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
smime.p7s
Description: S/MIME Cryptographic Signature
