Hacker News Reader

Comment by Bender | Hacker News Reader

I feel like they jumped the gun on this article. 3.22 does not have a merge-usr package/script in http://dl-cdn.alpinelinux.org/alpine/v3.22/main and 3.23 does not yet exist otherwise I would test the merge script right now on a throw-away VM. Looking at the merge request it appears the Finish step is not yet completed or the pipeline was skipped or I am reading this incorrectly. Perhaps they are just missing an estimated deployment date in the article.

View on HN

As TFA says, currently the usr-merge and the script for it is only in Edge, and it will come to stable in 3.23

I've read the article 5 times and I can almost interpret it that way in the how to migrate section which mentions 3.23. The Timeline section has no mention of dates. I would like to see a table of dates or at least an Oompa Loompa song.

There's no need to interpret anything. It's spelled out in the list in the Timeline section already. Point 1 tells you it's in Edge. Point 2 tells you that stable will be able to start migrating with 3.23, ie when current Edge becomes stable.

I am not seeing the same thing as you. The timeline section says that if I install 3.23 it will be user-merged and if I upgrade from an older release I wont be forced until 3.26. There are no dates. A timeline will have times and/or dates. Perhaps it is a CDN caching issue.

>>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.

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.

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.

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.

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.

Reply on news.ycombinator.com