You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by Ryan Blue <bl...@apache.org> on 2016/02/05 00:23:01 UTC
Moved to git!
The new git repository is live! You can clone it from here:
https://git-wip-us.apache.org/repos/asf/avro.git
It looks like the commit hashes are identical to the ones in the github
mirror, so it should just appear like trunk has been renamed to master
if you've already cloned the github mirror. In that case, just run this:
git remote add apache https://git-wip-us.apache.org/repos/asf/avro.git
The old SVN repository is still RW so we can change the site/ folders,
so please remember to push to the git repo's master instead of
committing code changes to SVN. Does anyone know if we still use those
folders? If not, then we can probably switch it over to read-only.
There are a few tasks that we will still need to do, like updating docs
[1] and the build.sh script. These are good starter issues if anyone out
there wants to become a contributor!
rb
[1]: https://issues.apache.org/jira/browse/AVRO-1794
--
Ryan Blue
Re: Moved to git!
Posted by Sean Busbey <bu...@cloudera.com>.
Do we want git release tags that match ASF policy for our older releases,
or just going forward?
They're supposed to look like "rel/_release_". Given our current tagging
strategy, that would make e.g. the 1.8 release "rel/release-1.8.0".
(the rel/ namespace doesn't allow tags to change once they're created)
On Thu, Feb 4, 2016 at 5:23 PM, Ryan Blue <bl...@apache.org> wrote:
> The new git repository is live! You can clone it from here:
>
> https://git-wip-us.apache.org/repos/asf/avro.git
>
> It looks like the commit hashes are identical to the ones in the github
> mirror, so it should just appear like trunk has been renamed to master if
> you've already cloned the github mirror. In that case, just run this:
>
> git remote add apache https://git-wip-us.apache.org/repos/asf/avro.git
>
> The old SVN repository is still RW so we can change the site/ folders, so
> please remember to push to the git repo's master instead of committing code
> changes to SVN. Does anyone know if we still use those folders? If not,
> then we can probably switch it over to read-only.
>
> There are a few tasks that we will still need to do, like updating docs
> [1] and the build.sh script. These are good starter issues if anyone out
> there wants to become a contributor!
>
> rb
>
>
> [1]: https://issues.apache.org/jira/browse/AVRO-1794
>
> --
> Ryan Blue
>
--
Sean
Re: Moved to git!
Posted by Niels Basjes <Ni...@basjes.nl>.
Hi,
I just noticed both these pages
http://avro.apache.org/version_control.html
https://cwiki.apache.org/confluence/display/AVRO/How+To+Contribute
have not been updated to reflect the change to git.
Can one of you guys pick this up please?
Niels Basjes
On Wed, Feb 10, 2016 at 5:13 PM, Sean Busbey <bu...@cloudera.com> wrote:
> On Tue, Feb 9, 2016 at 8:56 AM, Tom White <to...@cloudera.com> wrote:
>
> > On Thu, Feb 4, 2016 at 11:23 PM, Ryan Blue <bl...@apache.org> wrote:
> > > The new git repository is live! You can clone it from here:
> > >
> > > https://git-wip-us.apache.org/repos/asf/avro.git
> > >
> > > It looks like the commit hashes are identical to the ones in the github
> > > mirror, so it should just appear like trunk has been renamed to master
> if
> > > you've already cloned the github mirror. In that case, just run this:
> > >
> > > git remote add apache
> https://git-wip-us.apache.org/repos/asf/avro.git
> > >
> > > The old SVN repository is still RW so we can change the site/ folders,
> so
> > > please remember to push to the git repo's master instead of committing
> > code
> > > changes to SVN. Does anyone know if we still use those folders? If not,
> > then
> > > we can probably switch it over to read-only.
> >
> > The site folder (https://svn.apache.org/repos/asf/avro/site) contains
> > the website, so we do still need to able to write to it. As far as I
> > know, sites still use svnpubsub at the ASF so we need to keep these
> > pages in svn (see http://www.apache.org/dev/project-site.html).
> >
> > Tom
> >
> >
> There's a gitpubsub now, so we could move the site over to git if we so
> desired. It can either be a branch (asf-site) or it can be in its own git
> repo (useful if we want to automate site generation and publication at some
> point).
>
> --
> Sean
>
--
Best regards / Met vriendelijke groeten,
Niels Basjes
Re: Moved to git!
Posted by Sean Busbey <bu...@cloudera.com>.
On Tue, Feb 9, 2016 at 8:56 AM, Tom White <to...@cloudera.com> wrote:
> On Thu, Feb 4, 2016 at 11:23 PM, Ryan Blue <bl...@apache.org> wrote:
> > The new git repository is live! You can clone it from here:
> >
> > https://git-wip-us.apache.org/repos/asf/avro.git
> >
> > It looks like the commit hashes are identical to the ones in the github
> > mirror, so it should just appear like trunk has been renamed to master if
> > you've already cloned the github mirror. In that case, just run this:
> >
> > git remote add apache https://git-wip-us.apache.org/repos/asf/avro.git
> >
> > The old SVN repository is still RW so we can change the site/ folders, so
> > please remember to push to the git repo's master instead of committing
> code
> > changes to SVN. Does anyone know if we still use those folders? If not,
> then
> > we can probably switch it over to read-only.
>
> The site folder (https://svn.apache.org/repos/asf/avro/site) contains
> the website, so we do still need to able to write to it. As far as I
> know, sites still use svnpubsub at the ASF so we need to keep these
> pages in svn (see http://www.apache.org/dev/project-site.html).
>
> Tom
>
>
There's a gitpubsub now, so we could move the site over to git if we so
desired. It can either be a branch (asf-site) or it can be in its own git
repo (useful if we want to automate site generation and publication at some
point).
--
Sean
Re: Moved to git!
Posted by Tom White <to...@cloudera.com>.
On Thu, Feb 4, 2016 at 11:23 PM, Ryan Blue <bl...@apache.org> wrote:
> The new git repository is live! You can clone it from here:
>
> https://git-wip-us.apache.org/repos/asf/avro.git
>
> It looks like the commit hashes are identical to the ones in the github
> mirror, so it should just appear like trunk has been renamed to master if
> you've already cloned the github mirror. In that case, just run this:
>
> git remote add apache https://git-wip-us.apache.org/repos/asf/avro.git
>
> The old SVN repository is still RW so we can change the site/ folders, so
> please remember to push to the git repo's master instead of committing code
> changes to SVN. Does anyone know if we still use those folders? If not, then
> we can probably switch it over to read-only.
The site folder (https://svn.apache.org/repos/asf/avro/site) contains
the website, so we do still need to able to write to it. As far as I
know, sites still use svnpubsub at the ASF so we need to keep these
pages in svn (see http://www.apache.org/dev/project-site.html).
Tom
>
> There are a few tasks that we will still need to do, like updating docs [1]
> and the build.sh script. These are good starter issues if anyone out there
> wants to become a contributor!
>
> rb
>
>
> [1]: https://issues.apache.org/jira/browse/AVRO-1794
>
> --
> Ryan Blue