Post

Putting together release notes for 1.98 and realizing we have to make a decision soon. 2.0 or 1.100

19 reposts831 likes

Does SemVer have any specified utility for apps? If not I’d be treating the major version segment more for branding/marketing, and let the minor/patch increment automatically with no real practical upper bound.

The major is supposed to indicate a lack of backwards compatibility because the public API changed in such a way that a 1.98 app can't use all the API endpoints that were available when it was published

Semver only gives way to marketingver just ahead of a major conference, so it depends on if you’re going to hotfix just ahead of SXSW. But if you’re gonna skyver, I’d do 1.99999 just to make some eyeballs twitch more

2.0 could be: * edit posts * 4x character limit increase * time outs (short term block) * (optional) approve new follower - not acting on it for 1 week means "nope" * remove follower yeah, that's all doable (edit posts gets in the weeds)

Um… 1.100 - save 2.0 for whatever version allows us to upload gifs directly from our devices (and work properly). Also, 2.0 should have its own dedicated iPadOS layout. I don’t know how any of that actually works. I just know I couldn’t have Android 2.0 until some of the major basics were fixed.

Introduce Group DMs & allow image and video upload in the DMs. Massive change and would bring over a bunch of OSINT guys who still hesitate to use Bluesky for this exact reason.

Break the part that forces me to drill 8 clicks down just to add an image, then promptly forgets where it just looked one post ago. Kudos for not grabbing the first image and running with it, forcing you to go back for more images, like a *certain* unnamed site. But surely you can top 4.🤔 [==*==]

Hi Mr Semver here (not joking) it’s fine to release a non-breaking 2.0.0. You MUST if you have breaking ones, but it says nothing about that only being acceptable when there is breakage.

You can and should do 1.100. That is more correct than 2.0. You presumably did 1.1 and 1.10, so adding another zero doesn’t change the correctness.

My brother, y'all can and should do whatever you want with your version numbers. Chromium is on version 753 or whatever now, and at the rate they go, it'll be like 1035 by the end of the month, and nobody says shit to them about it.

folks at work simply refuse to go over version 4.3 in our scripts package. no matter the level of modification. we're on 4.3r. it's been 4.3 for almost 10 years

I break the number into <level>.<version>, where <version> is for minor changes and fixes, while <level> represents fundamental enhancements that introduce entirely new functionality, appearance, and/or changes to operability. By my estimation, you should already be closer to 5.1 than 2.0. [==*==]

I had a client that I loved (paid well, lots of creative freedom) BUT every time we would make changes to the restaurant menu the file that got sent to the printer was something like "menuFranchise_v8_final_PRINT.pdf". Every. Time. For six different shops.

I am confident our handsome and talented developer will make the correct decision and, in due time, my devices will update and inform me what it is.

*Somebody* will make an argument for finally acknowledging the lowly thousandths digit, but personally, I like to skip over a ".0" release and go straight to n.1. It looks more official. 😉 [==*==]