0.9.37 has been retagged

[dvzrv]

Hi! :wave:

This release has been retagged (similar to 0.9.34 in #401). via https://gitlab.archlinux.org/archlinux/packaging/packages/qtractor/-/issues/2

The relevant diff between a source tarball downloaded on 2023-12-05 and now is:

--- old/qtractor_0_9_37.tar.gz
+++ qtractor_0_9_37.tar.gz
│ ├── qtractor-qtractor_0_9_37/src/appdata/org.rncbc.qtractor.metainfo.xml
│ │ ├── qtractor-qtractor_0_9_37/src/appdata/org.rncbc.qtractor.metainfo.xml
│ │ │ @@ -43,11 +43,11 @@
│ │ │      <keyword>Qt</keyword>
│ │ │    </keywords>
│ │ │    <url type="homepage">https://qtractor.org</url>
│ │ │    <project_group>rncbc.org</project_group>
│ │ │    <developer_name>rncbc aka. Rui Nuno Capela</developer_name>
│ │ │    <update_contact>rncbc@rncbc.org</update_contact>
│ │ │    <releases>
│ │ │ -    <release version="0.9.37" date="2023-17-05" urgency="low"/>
│ │ │ +    <release version="0.9.37" date="2023-12-05" urgency="low"/>
│ │ │    </releases>
│ │ │    <content_rating type="oars-1.0"/>
│ │ │  </component>

Full diffoscope output: qtractor-0.9.37-diffoscope.log

@rncbc please just create a new tag. Retagging breaks downstream packaging and reproducibility. There really is no need for a ticket like this.

[rncbc]

said it before and now sayng it again:)

• GH is NOT the official release repo, never was; please, don't count on this to trigger a release tag as being GA, whatsoever;
• upstream (me) has the legit prerogative to retag a release as seems fit, always, as long it's done before the corresponding official release annoucement;
• the official release tarball is https://download.sf.net/qtractor/qtractor-0.9.37.tar.gz ; please don't trust anything else, even less so for the archives provided through GH.

sorry for all inconvenience. cheers

[dvzrv]

GH is NOT the official release repo, never was; please, don't count on this to trigger a release tag as being GA, whatsoever;

Sure, but does that matter, if the sources are the same? I'm interested in the git tags and auto-generated tarballs, not in any platform-specific releases (since this repository does not use any git submodules).

upstream (me) has the legit prerogative to retag a release as seems fit, always, as long it's done before the corresponding official release annoucement;

That doesn't doesn't break downstreams any less (e.g. also anyone that has the repository checked out).

Why not create pre-release tags, if something is not yet clear or needs figuring out? I mentioned in https://github.com/rncbc/qtractor/issues/401#issuecomment-1636737300 already, that it's not feasible for downstreams to wait for some bespoke message on some $platform for all of their upstreams. It does not scale. :)

the official release tarball is https://download.sf.net/qtractor/qtractor-0.9.37.tar.gz ; please don't trust anything else, even less so for the archives provided through GH.

For tracking purposes I would need to rely on regex matching in an HTML page to find new releases. Additionally, sourceforge has proven flaky and slow in the past. Git is far more reliable for this.