[Arnavion]

>>the Merge Request that finalizes the initial work will be merged. Any new __edge__ installations will be /usr-merged from this point onwards.

>>Release of Alpine Linux __3.23: [...] From this point onwards,__ users are encouraged to migrate existing installs.

[thomascountz]

Not OP, but I think OP is looking for dates, as in a year, month, day, situation—not only version numbers. I think they want to know what specific date 3.23 will be released with this change.

[Arnavion]

They didn't understand the version numbers (notice they were complaining that the blog post jumped the gun because there is no merge-usr in 3.22) and wanted dates. I explained the version numbers to them. Yes, there are no dates; Alpine never gives expected dates for future releases because nobody knows what they are.

[thomascountz]

I think I understand where there was confusion. I only commented because, as of my reading of the comments, OP clarified they were looking for a date, and your reply repeated version numbers. Perhaps they were originally asking for clarification of the version number (though I don't believe they were, based on the original comment, as written now), but their reply specifically referenced there being no dates. Perhaps they do not know that Alpine does not provide dates? Your reply suggests you might have misinterpreted that.

To OP: this announcement from Alpine doesn't contain dates, like you've mentioned. This is apparently not an accident.

[Bender]

I totally understand the version release methods. Ive been using Alpine as long as it has existed. Ive installed it manually and automated to thousands of nodes. This is however a breaking and major change so I would expect an actual timeline of when people can test it and when it will be mandatory using dates. I believe this is a reasonable ask.