next candidates for Git migration

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

next candidates for Git migration

Hervé BOUTEMY
now we have 15 git repos: 9 Git-WIP + 6 GitBox
I didn't try the git modules strategy to have an easy clone/pull: if somebody
tried, please share results

let's see the next candidates [1], which are less obvious than the 15 first
ones:

- 2 sites (Maven and Doxia): anybody knows if CMS supports source in Git?

- 2 parent poms: ASF and maven-parent. Seems feasible to have 2 repos. Only
issues I see are:
  - how to name the repo for ASF?
  - how to get the history for maven-parent, given there were a lots of moves?

- 6 resource bundles: http://maven.apache.org/apache-resource-bundles/
what about doing 1 git repo only, with one unique common version?

- 2 skins: seems feasible to have 2 repos (I don't know if getting history is
easy or not)

- 5 doxia tools: 5 repos seems reasonable

- 41 plugins
- 26 shared components
really, this will be the hard parts...

- archetypes: looks it has moved to 10 independant archetypes


The beginning of the list seems feasible: not as easy as previously, but
feasible
Are there volunteers to prepare reference target git repos?

If we can't get the job done on these, I think that talking about plugins
+shared+archetypes is just a waste of time

Regards,

Hervé


[1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: next candidates for Git migration

stephenconnolly
On Sun 22 Oct 2017 at 17:42, Hervé BOUTEMY <[hidden email]> wrote:

> discussing with infra, one day, everything should move to GitBox: but they
> didn't provide ETA
>
> let's discover GitBox and see if it deserve to ask for migration without
> waiting


Just may be confusing to committers having to jump back and forth between
the two... plus the different feature sets.

We’ll have people either not being aware of the greater features with
gitbox or hitting the wall of lesser features on git-wip-us

I’m fine with giving a little time to check out how gitbox works, but IMHO
it doesn’t make good sense to split a project’s repos between three
different hostings... (ok when we migrate off svn we’ll be down to two...
but that still doesn’t make sense)


>
> Regards,
>
> Hervé
>
> Le dimanche 22 octobre 2017, 17:50:23 CEST Stephen Connolly a écrit :
> > Should we see about moving our git-wip to gitbox?
> >
> > On Sun 22 Oct 2017 at 15:12, Hervé BOUTEMY <[hidden email]>
> wrote:
> > > now we have 15 git repos: 9 Git-WIP + 6 GitBox
> > > I didn't try the git modules strategy to have an easy clone/pull: if
> > > somebody
> > > tried, please share results
> > >
> > > let's see the next candidates [1], which are less obvious than the 15
> > > first
> > > ones:
> > >
> > > - 2 sites (Maven and Doxia): anybody knows if CMS supports source in
> Git?
> > >
> > > - 2 parent poms: ASF and maven-parent. Seems feasible to have 2 repos.
> > > Only
> > >
> > > issues I see are:
> > >   - how to name the repo for ASF?
> > >   - how to get the history for maven-parent, given there were a lots of
> > >
> > > moves?
> > >
> > > - 6 resource bundles: http://maven.apache.org/apache-resource-bundles/
> > > what about doing 1 git repo only, with one unique common version?
> > >
> > > - 2 skins: seems feasible to have 2 repos (I don't know if getting
> history
> > > is
> > > easy or not)
> > >
> > > - 5 doxia tools: 5 repos seems reasonable
> > >
> > > - 41 plugins
> > > - 26 shared components
> > > really, this will be the hard parts...
> > >
> > > - archetypes: looks it has moved to 10 independant archetypes
> > >
> > >
> > > The beginning of the list seems feasible: not as easy as previously,
> but
> > > feasible
> > > Are there volunteers to prepare reference target git repos?
> > >
> > > If we can't get the job done on these, I think that talking about
> plugins
> > > +shared+archetypes is just a waste of time
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > >
> > > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> > > --
> >
> > Sent from my phone
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
> --
Sent from my phone