Planning a v5.3.8 bug fix release

Announcements
1

Frustratingly, we need to release a v5.3.8 to fix a critical bug that was introduced in v5.3.7.

I propose to make the release on Monday 28th July 2025 Thursday 7th August 2025. This is a bug fix release that will not contain any other updates or improvements.

The critical bug concerns a change to the list-tagged-draggable macro that is not fully backwards compatible.

UPDATE 18th July 2025: The problem with Projectify was not the PR linked above, but turned out to be a different PR which updated some core macros to be procedures.

It is discussed further here:

This problem was uncovered by a user who ran into difficulties with the Projectify plugin, a very popular plugin. The problem occurs when dragging and dropping to reorder tasks, and so is likely to affect almost all users of the plugin.

It was undoubtedly a mistake to have merged this change. It was also a shame that we didn’t find the problem during the testing period before the v5.3.7 release. It would only have come to light if somebody had upgraded a wiki that used Projectify and methodically tested the functionality. The next time we announce the testing period for a release I will make sure to expand on the suggested testing strategy.

One further point was that we will need a revised banner image. @Christian_Byron would you be able to prepare an update to replace my temporary placeholder?

Unknown2
Unknown2560×315 37.7 KB

4 Likes
Preparing for Release of TiddlyWiki v5.3.7 on Monday 7th July 2025
2

Pinned till 21st July 2025 - 12:00 UTC

3

I actually like your temporary placeholder! :wink:

7 Likes
4

I even think a crude graffiti type “cross out and updated digit” like that is a really cool general solution for bug fix releases (which do happen every now and then).

5 Likes
5

I agree that the hand-drawn revision is very good .. but just so you have the option, here is mine revised with the new number

TW3.5.8 Banner Entry
TW3.5.8 Banner Entry560×315 121 KB

3 Likes
6

Thank you @Christian_Byron. I’m concerned that the joke might wear thin before we get to the v5.4.0 release. Perhaps it would be fun to have the people decide:

  • Use the graffitied v5.3.7 banner for v5.3.8
  • Use the new, clean banner for v5.3.8

0 voters

7

We’ve discovered that the PR that I originally linked to is not the culprit for the problem with Projectify. I’ve updated the OP with more details.

8

I think it is a fun joke and I do like the “scribbles” and the freehand 8. IMO it fits very well for the prerelease.

IMO in the long run it may communicate the “wrong” message for new users, that do not know TiddlyWiki yet.

It is not obvious, that it is a bugfix release. While funny for insiders, the image may communicate a “hasty and unfinished, release”. – Just my thoughts.

1 Like
9

Aha! - we should make all regular releases as scribbles and the bug fix releases pretty! :wink:

10

I was on the fence, and this swayed me to vote for the clean.

I think an “update of the previous” sort of idea could work with some artistic fine tuning. Like maybe a stamp over the top of the 7 with an 8, or a masking tape covering the 7, with 8 written on it. Something that balanced the message of “this is an update to a previous” but without the scribble implementation. (maybe a scribble that turns the 7 into an 8 even - which is not an opportunity you get with many sequential numbers)

11

Great, thanks everyone for the feedback. I think it’s clear that we should indeed use @Christian_Byron’s updated artwork, and so I’ve gone ahead and replaced the graffitied version.

12

Too late for the vote, but even though I brought up liking the graffiti, I would have voted for the more professional one for the same reasons mentioned above. It’s cute, but in-jokes don’t belong on public-facing artifacts.

Source code comments, though, are fair game!

3 Likes
13

@jeremyruston – This PR should be part of v5.3.8 Fix sidebar tools version for v5.3.8 by pmario · Pull Request #9165 · TiddlyWiki/TiddlyWiki5 · GitHub

14

These small fixes are ready to be included in v5.3.8:

1 Like
15

Please revert this PR or make the title field the default field to show by list-tagged-draggable. This PR has affected several of kookma plugins including the popular Favorites plugin.

2 Likes
16

Please note that a bug fix release should only includes fixes for bugs introduced in the previous release, to reduce the risk of inadvertently introducing new problems.

I concur with @Mohammad that #8721 should be reverted for v5.3.8.

1 Like
17

It has been reverted. Revert "list-tagged-draggable shows caption field if it is available" by Jermolene · Pull Request #9156 · TiddlyWiki/TiddlyWiki5 · GitHub

18

@pmario it was reapplied: Reapply "list-tagged-draggable shows caption field if it is available… · TiddlyWiki/TiddlyWiki5@89030c4 · GitHub

1 Like
19

Hi @pmario
To reach a compromise that maintains both your improvement and backward compatibility, I submitted a PR (Revert the list-tagged-draggable to use title field by default by kookma · Pull Request #9177 · TiddlyWiki/TiddlyWiki5).

This PR uses the title field as the default unless the user specifies the desired field for the list-tagged-draggable macro. I updated the macro header as follows:

\define list-tagged-draggable(tag,subFilter,emptyMessage,
itemTemplate,elementTag:"div",storyview:"",field:"title")

Also in the body:

<$transclude tiddler="""$itemTemplate$""">
	<$link to={{!!title}}>
		<$let tv-wikilinks="no">
			<$transclude field=<<__field__>>>  <----------------------look here---
				<$view field="title"/>
			</$transclude>
		</$let>
	</$link>
</$transclude>
2 Likes
20

Thank you everyone and my apologies that I am a little behind after some medical issues earlier in the week.

As @saqimtiaz says, this release should only include fixes for regressions introduced in v5.3.7. I’ve made the following changes:

  • Reverted #8721 (“list-tagged-draggable shows caption field if it is available”) by applying #9182
  • Applied #9165 (“Fix sidebar tools version for v5.3.8”)

Let me know if I’ve missed anything.

5 Likes