Planning for the release of v5.3.0

[Jermolene]

The following roadmap is proposed for the upcoming v5.2.6 release and the following v5.3.0 release:

• 6th March 2023 : final date for merging pull requests for v5.2.6
• 20th March 2023: release of v5.2.6
• (20th - 27th March 2023: window for release of v5.2.7 if required due to bugs in v5.2.6)
• 19th April 2023: merge Parameterised transclusions #6666 into master
• 16th June 2023 24th June 2023: final date for merging pull requests for v5.3.0
• 28th June 2023 30th June 2023: release of v5.3.0

[Jermolene]

Due to #7371 we are going ahead with a v5.2.7 bug fix release on Sunday 26th March. See #7372 for the planning discussion.

[pmario]

Related: Tickets to be reviewed/merged after release of v5.2.6 #7345

[Jermolene]

I've updated the roadmap to reflect the delay caused by the v5.2.7 release.

[Jermolene]

I've updated the roadmap now that #6666 has been merged.

[rmunn]

I'd like to get #7448 reviewed so that the checkbox listField bug can be fixed before 5.3.0. See #6871 for the details of the bug; #7448 fixes the last outstanding issue, where the created and modified fields could be messed up if you pass them into a checkbox widget's listField parameter.

Edit: Thanks for the quick review & merge.

[pmario]

@Jermolene .. Since the "closing date for PRs" is near, imo the Tickets to be reviewed/merged after release of v5.2.7
#7345 needs to be reviewed again.

Especially, there is the PR: Bidirectional text improvements #4541 which seems to be a big improvement, but is not yet merged. IMO @kookma should give a statement about that one.

[pmario]

@Jermolene ... Does this plan still stand?

[Jermolene]

@Jermolene ... Does this plan still stand?

Yes; I'll update this plan if anything changes (I've already updated it a couple of times).

[Jermolene]

I've updated the OP to change the PR freeze date to today, 24th June 2023, and to change the final release date from 28th June to 30th June.

Tagging @twMat because he was asking elsewhere about changes to the release timetable.

[pmario]

Should we open a "Final Test Request for v5.3.0" at Talk, which I could globally pin for the next week?

[pmario]

.. and I'll update the German texts today :)

[Jermolene]

Should we open a "Final Test Request for v5.3.0" at Talk, which I could globally pin for the next week?

Yes thank you, I shall make a post shortly

[twMat]

Tagging @twMat because he was asking elsewhere about changes to the release timetable.

@Jermolene - appreciated.

Should we open a "Final Test Request for v5.3.0" at Talk, which I could globally pin for the next week?

For this, may I propose to explicitly include something along the lines of:

"It is suggested that you use a copy(!) of your real life wikis, i.e complex wikis that you've tweaked and personalized over a long time, so that the new version is tested under tough conditions"

[Jermolene]

Thanks @twMat – I made an announcement post at https://talk.tiddlywiki.org/t/final-checks-before-release-of-v5-3-0/7398