On 26/2/25 04:26, Jonathan Riddell wrote:
Spectacle update
- <td><a
href="http://download.kde.org/stable/plasma/6.3.2/spectacle-6.3.2.tar.xz";>spectacle-6.3.2</a></td>
+ <td><a
href="http://download.kde.org/stable/plasma/6.3.2/spectacle-6.3.2.1.tar.xz";>spectacle-6.3.2.1</a></td>
<td align="right">1.4MB</td>
-
<td><tt>12362c0e4b01b405f8be68b4d4b59fb92082784eddddaa69c212f0c5106470e6</tt></td>
+
<td><tt>df1d33ebab501ef4bf658d4c894a870c3fe648bd836c5fc5ee20587cde093cee</tt></td>
I'd like to propose we (KDE) take a look at our release process, QA and
testing. In the last few weeks we've had 4 re-spins after release.
Are these re-spins due to show-stopping bugs? If not then we should just
wait until the next release.
If they are show-stopping, this indicates we need more testing in my
opinion. Whether that is human or automated doesn't matter provided we
catch these before release.
Regards,
A KDE contributor/user concerned about our quality.
