Please make a python-glib release - is there a hold up?
raf at durin42.com
Fri Dec 30 17:17:53 EST 2016
> On Dec 29, 2016, at 4:44 PM, Idan K <idankk86 at gmail.com> 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 releases and that’ll be a start.
> On Thu, Dec 29, 2016 at 10:11 PM, Augie Fackler <raf at durin42.com <mailto:raf at durin42.com>> wrote:
> 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 Scott <barry at barrys-emacs.org <mailto:barry at barrys-emacs.org>> wrote:
> > 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
> > Mercurial-devel at mercurial-scm.org <mailto:Mercurial-devel at mercurial-scm.org>
> > https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel <https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mercurial-devel