> On Jan 3, 2017, at 17:24, Matt Mackall wrote:
>
> On Thu, 2016-12-29 at 15:11 -0500, Augie Fackler wrote:
>> At the moment, only mpm and idank (cc’ed) can do a release. Perhaps one of
>> them can do so?
>
> I've cut and pushed a 2.3 release, sorry for the delay. The official
On Thu, 2016-12-29 at 15:11 -0500, Augie Fackler wrote:
> At the moment, only mpm and idank (cc’ed) can do a release. Perhaps one of
> them can do so?
I've cut and pushed a 2.3 release, sorry for the delay. The official hglib repo
still lives on my server, so a bit of infra work will need to be
Done.
On Sat, Dec 31, 2016 at 12:17 AM, Augie Fackler wrote:
>
> On Dec 29, 2016, at 4:44 PM, Idan K wrote:
>
> I don't have commit access to the repo though, so can't tag a release.
>
> Happy to make whatever changes to the package on PyPI.
>
>
> If you
> On Dec 29, 2016, at 4:44 PM, Idan K wrote:
>
> I don't have commit access to the repo though, so can't tag a release.
>
> Happy to make whatever changes to the package on PyPI.
If you add `durin42` on PyPI as an owner, I can add the other people that are
able to make hg
I don't have commit access to the repo though, so can't tag a release.
Happy to make whatever changes to the package on PyPI.
On Thu, Dec 29, 2016 at 10:11 PM, Augie Fackler wrote:
> At the moment, only mpm and idank (cc’ed) can do a release. Perhaps one of
> them can do so?
At the moment, only mpm and idank (cc’ed) can do a release. Perhaps one of them
can do so?
Also, we should probably unify the list of people that can do hglib releases
with the list of people that can do hg releases. Thanks for mentioning this
oversight.
> On Dec 29, 2016, at 1:35 PM, Barry
It has been a while since my patches where accepted, but there is no PyPi
release with the changes yet.
Is there some process that I need to follow to get a python-glib release made?
Barry
___
Mercurial-devel mailing list