Library release removal request

[christandlg]

Library name

AS3935MI

Version to remove

1.3.5

[per1234]

Hi @christandlg. You must delete the 1.3.5-beta tag from the library's BitBucket repository before we can remove the release. I see that it has not yet been removed:

https://bitbucket.org/christandlg/as3935mi/src/1.3.5-beta/library.properties

Once you have removed the tag from the BitBucket repository, comment here to let me know that the tag has been deleted so that I can proceed with removing the release from Arduino Library Manager.

[christandlg]

Hi @per1234 ,
the original tag was 1.3.5, i deleted it and created 1.3.5-beta instead. Library version in library.properties is 1.3.5.
Does the tag still need to be removed?

[per1234]

@christandlg if we remove the existing 1.3.5 release, the indexer is going to then immediately generate a new 1.3.5 release from the repository at the 1.3.5-beta tag. Although tags are the unit of release for Library Manager, versioning is done exclusively according to the version property of the library.properties metadata file. The tag name is completely ignored.

So if you intend to make a new 1.3.5 release of the library using the codebase at tagged 1.3.5-beta point in the revision history, then we can proceed with the removal. If you don't want to do that, then you must remove the tag. Please let me know how to proceed.

Please note that making multiple releases with the same version number is a terrible development practice. We allow library maintainers to request release removals in emergencies where a release contains something that absolutely must not be distributed (e.g., copyrighted material you don't have permission to distribute). We do not offer this service to allow library maintainers to get a "do over" when there is a problem with a release.

In the case that there is a non-emergency problem with a release, the responsible thing to do is to simply fix whatever was wrong in the problematic release and then make a new release with a new version. This is a better approach because:

• The new release will be published in a matter of hours by the automated Library Manager system. Conversely, it may take days or weeks for us to find time for the manual work required to accommodate a removal request.
• Users who already installed the bad release will get an update offer for the new release. Conversely, if you re-release then anyone who already installed the bad release will not get an update.
• Users would find it quite confusing for there to have been two releases with the same version number but technical differences in the library.

[christandlg]

@per1234 thank you for the clarification.
I created this issue because library functionality is broken. I will restore the 1.3.5 Tag and create a new release of the lib (with new version number) asap, and hereby cancel my request.