So we do have a gerrit issue, or we don't?
It's not clear to me through this infra thread if there was a hiccup in
tagging.
Granted, we're dropping down to just maintaining 3.8 and 3.10 so not quite
as much tagging for releases, but if there's something that needs to be
documented before the move i
Vijay pushed the tag. So didn't file any bug. It is sorted out. We just
need help with hosting rpms on download.gluster.org
On Tue, Feb 28, 2017 at 10:24 AM, Amye Scavarda wrote:
> Hi all,
> So I believe this got tagged earlier, but what was the resolution here?
> I don't see a bug filed, did I
Hi all,
So I believe this got tagged earlier, but what was the resolution here?
I don't see a bug filed, did I miss it?
- amye
On Mon, Feb 27, 2017 at 6:25 AM, Nigel Babu wrote:
> File a bug, please.
>
> On Mon, Feb 27, 2017 at 7:03 PM, Prasanna Kalever
> wrote:
>
>> Hi,
>>
>>
>> We seem to b
File a bug, please.
On Mon, Feb 27, 2017 at 7:03 PM, Prasanna Kalever
wrote:
> Hi,
>
>
> We seem to be having access issues in tagging v0.1 release for
> gluster-block.
>
> This is what I see,
>
> $ git push --tags gerrit master
> All keys already loaded
> Counting objects: 1, done.
> Writing ob
Hi,
We seem to be having access issues in tagging v0.1 release for gluster-block.
This is what I see,
$ git push --tags gerrit master
All keys already loaded
Counting objects: 1, done.
Writing objects: 100% (1/1), 183 bytes | 0 bytes/s, done.
Total 1 (delta 0), reused 0 (delta 0)
remote: Proces
