Re: How does team maintenace of python module works?
On 02/20/2013 04:31 PM, Luca BRUNO wrote:
> This may suit well for the openstack scenario, however in general I
> could see at least two shortcomings:
> * pristine upstream tarballs are not used (see the first "should" in
> devref §6.7.8.2)
> * it assumes that no tarball generation process (eg. make dist) is
> needed
>
> I'm not sure how much impact they have on normal python-team workflow,
> though.
>
> Cheers, Luca
I agree it only fits cases where upstream uses git and tags.
Though it's a more and more common case. Some upstream
authors don't even care to release a tarball at all nowadays.
Thomas
Reply to: