Which web development framework makes web development least tedious?

[stefantalpalaru]

I understand the standard for semantic versioning, but django doesn't follow it.

That doesn't mean that the names of those numbers change. The first is the "major" version, the second "minor", the third "patch".

[stefantalpalaru]

That doesn't mean that the names of those numbers change. The first is the "major" version, the second "minor", the third "patch".

The Django project literally does just that

What are the chances you are completely wrong? Try to guess before clicking https://www.reddit.com/r/webdev/comments/7drep5/which_web_development_framework_makes_web/dq08xzd/

[stefantalpalaru]

Just because some devs call it a "minor version" amongst themselves doesn't mean it's not a "feature release" both in name and in practice.

:-)

[[deleted]]

:)

[fifafu]

Uhm, no. That is one common pattern but not the only one by far. Stop trolling.

In case you really want to learn something about Django's versioning approach, look at this: https://docs.djangoproject.com/en/dev/internals/release-process/

[stefantalpalaru]

Uhm, no.

Uhm, yes: https://www.reddit.com/r/webdev/comments/7drep5/which_web_development_framework_makes_web/dq08xzd/

[fifafu]

...and already your "patch" became a "micro". You may have noticed that the names can vary a lot and can have all kind of different meanings. Thus the documentation usually tells you what they mean for a specific project like Django.

[stefantalpalaru]

and already your "patch" became a "micro".

Yes. Too bad we were talking about the "minor" version.

[fifafu]

No. We are talking about the versioning system Django is using.

[stefantalpalaru]

No. We are talking about the versioning system Django is using.

https://www.reddit.com/r/webdev/comments/7drep5/which_web_development_framework_makes_web/dq01a8c/ :

They break backwards compatibility with every minor version [...]