I am only talking about the SCM URLs in Maven. Not the general work. Everyone can still use Github for the daily work. In fact I would even recommend that. Only for releases we use Gitbox (but that is enforced by the maven-release-plugin together with the SCM info in the pom.xml) so no need for a developer to worry/care about that specifically. That means you can do releases (in fact from Gitbox) even if your local clone is from Github.
> On 10. Oct 2017, at 12:36, Robert Munteanu <[email protected]> wrote: > > On Tue, 2017-10-10 at 12:31 +0200, Bertrand Delacretaz wrote: >> On Tue, Oct 10, 2017 at 12:26 PM, Robert Munteanu <[email protected] >>> wrote: >>> ...Together with Konrad's notes on the Maven release plugin this >>> makes a >>> pretty strong case for using gitbox as the canonical URL >>> everywhere... >> >> But we do other things much more often than releases, so it's hard to >> give up the convenience... >> >> I don't have a better suggestion right now but I'm sure we can find a >> convenient way to use GitHub for day-to-day work and gitbox for >> releases. A Maven profile maybe? >> >> -Bertrand > > It should be fine to clone from and push to GitHub, but release from > GitBox. After all, the commit hashes are the same and tags will be > propagated to GitBox instantaneously. > > Or at least we'll know once we run the first release :-) > > Robert
