I'm a bit confused by the conversation so far. Can someone elaborate on "maintainers have explicitly pushed their tags to the ELPA repo"? I do tag all the releases of my packages, as that's a common (and good) practice, but I don't understand why would something like this be affecting ELPA negatively. Does it sync the tags from the remotes or what? 

In general I don't think that something like "stop tagging your releases upstream" is a good solution. Adding a prefix to the tag name (e.g. the package name) also seems weird in the context of a single project repository. 

On Wed, Aug 18, 2021, at 5:30 AM, Phil Sainty wrote:
> On 2021-08-18 11:36, Eric Abrahamsen wrote:
> > Okay, this is really useful! Thank you. So it's only an issue if 
> > package
> > maintainers have explicitly pushed their tags to the ELPA repo. So all
> > the README needs to say, really, is "don't push your tags to the ELPA 
> > repo".
> 
> Yes, I think so; although it might be worthwhile elaborating to avoid
> any potential confusion.  Something like:
> 
> Git tags should not be pushed to the ELPA repository.  This is because:
> 
> * Tags are global throughout any git repository.
> 
> * Therefore tags sourced from one package might conflict with tags
>    sourced from another project (e.g. a version tag "1.0").
> 
> * The ELPA repository doesn't need any tags.
> 
> Note that git will not push any tags unless you explicitly tell it to
> do so.
> 
> 
>