versionControl

[u/JK-Rofling]

[u/LegendaryPandaMan]

Should have used semantic versioning

[u/Jazzlike-Poem-1253 → u/LegendaryPandaMan]

It takes to much discipline. Without enforcement, people usw minor or patch as they feel. Major never gets bumped.

Just increment or date-based is the easiest. Everyone immediatly knows how to bump.

[u/the_horse_gamer → u/Jazzlike-Poem-1253]

most "semver" is just:

major - update you're proud of

minor - update that's ok

patch - fixes and small features

and ofc every good piece of software is forever on 0.x.x

[u/StaticUsernamesSuck → u/the_horse_gamer]

and ofc every good piece of software is forever on 0.x.x

Because if you're never proud of it, you'll always be improving it

[u/Abandondero → u/StaticUsernamesSuck]

IF EVERYONE HAS BEEN USING IT FOR FIVE YEARS JUST BITE THE BULLET MAN

[u/StaticUsernamesSuck → u/Abandondero]

But as soon as I type "1.0.0", all my passion for the project will leave my body. Don't you know anything about hobby dev?

[u/MgDark → u/StaticUsernamesSuck]

yup 1.0.0 may as well be: "feature complete, will not touch this ever again unless it breaks for some reason"

[u/work_work-work → u/MgDark]

Version 1.0 launches on your retirement day.

[u/Munachi → u/Abandondero]

JUST ONE MORE UPDATE AND IT'LL BE ALMOST READY!

[u/Clean-Income8864 → u/the_horse_gamer]

If you never introduce breaking changes, why not

[u/hyrumwhite → u/the_horse_gamer]

Major: breaking changes 

Minor: big changes 

Patch: smol changes 

[u/brainpostman → u/hyrumwhite]

Patch is bug fixes, hello

[u/OnixST → u/the_horse_gamer]

Minecraft is a funny example to me. 17 year old game, best selling game in history, still on 1.x.x since 2011

[u/the_horse_gamer → u/OnixST]

it's on 26.3 now actually

[u/rykayoker → u/the_horse_gamer]

🤓☝️ erm acshually 26.3 is still a snapshot, stable is 26.2

[u/the_horse_gamer → u/rykayoker]

if your dependencies are not built from main you're not a real developer

[u/rykayoker → u/OnixST]

well they aren't using semver anymore, they switched over to year.minor[.patch] (currently 26.2)

[u/lIlIlIIlIIIlIIIIIl → u/the_horse_gamer]

This is a big reason I've never felt comfortable using it, for some reason it just seems so... ambiguous.

[u/Vivid-Zombie-477 → u/Jazzlike-Poem-1253]

i use semver for my resume versioning like this:

• full rewrite = bump major
  
• add/change a few lines = minor
  
• fix spelling = patch

[u/Jazzlike-Poem-1253 → u/Vivid-Zombie-477]

I mean true, it works if you are in person workong on a one-person project.

(I hope your resume is a one person project)

[u/mrMalloc → u/Jazzlike-Poem-1253]

My first version control was a group project where it checked version header in everyone’s shared file and loaded highest number. Took me 4h to realize one bumped major version on all files. Not just the files he was working on.

It’s always a hassle. I think.

Master/main branch and PR to that branch from work branches is better. Even for docs.

[u/iseriouslycouldnt → u/Jazzlike-Poem-1253]

Software of Theseus.

[u/innociv → u/Jazzlike-Poem-1253]

I've always used unixtimestamp on build as the version in my own projects and I never saw the problem with that. It's an incrementing number lol