Actually; Isn't it a matter of asking for a new one? We should be able to migrate the content ourselves, as in a few minutes.
Or? On Sun, Jul 19, 2015 at 9:33 PM, Niclas Hedhman <[email protected]> wrote: > > I think a repo rename is reasonable. I'll raise a ticket and see what > infra says. > > Cheers > Niclas > > On Sun, Jul 19, 2015 at 6:50 PM, Paul Merlin <[email protected]> wrote: > >> Hey Sandro, >> >> Sandro Martini a écrit : >> > Hi Paul, >> > I think a rename now would be better now, but maybe the same rename >> > should be done in many other places (docs, etc) to reduce possible >> > confusion even there. >> We already renamed everything except java packages for 2.1 (in order to >> keep backward compatibility with 2.0). >> See the `develop` documentation >> at:https://zest.apache.org/java/develop/index.html . >> >> In 3.0 we will rename the java packages, see ZEST-40. >> >> To rename the git repository we need to open a INFRA issue. >> Then we should impact builds.apache.org jobs configuration, and of >> course, our git clones. >> Am I right? >> >> Cheers >> >> /Paul >> >> > > > -- > Niclas Hedhman, Software Developer > http://zest.apache.org - New Energy for Java > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
