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 <[email protected]> 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
