Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to version front-end projects?

Semantic versioning brings the follow approach:

  • MAJOR version when you make incompatible API changes
  • MINOR version when you add functionality in a backwards-compatible manner
  • PATCH version when you make backwards-compatible bug fixes

However a frontend project doesn't have an API, its doesn't break compatibility of usage, then, what the arguments to change the versions in frontends?

Please, sugestions.

like image 364
Luan Kevin Ferreira Avatar asked Sep 07 '17 21:09

Luan Kevin Ferreira


People also ask

What is version control in front end?

A component of software configuration management, version control, also known as revision control or source control, is the management of changes to documents, computer programs, large web sites, and other collections of information.

Why should you use versioning?

Software versioning is important because it helps both users and software providers track the different versions that the company releases. Users rely on software developers to keep them up to date, and they expect a methodical way of understanding when and what updates are released.

Is JavaScript for front end?

HTML, CSS, and JavaScript are the languages used for Front End development. The structure, design, behavior, and content of everything seen on browser screens when websites, web applications, or mobile apps are opened up, is implemented by Front End developers.


1 Answers

Proposal

Given the importance of the installation-requirements of an application to installer-users, I propose that semver be used to version end-user applications using the installation-requirements as the public API with installer-users as the consumers of this API. In practice, increment the:

• MAJOR version when you make incompatible API changes (e.g. installer-users have to modify their infrastructure (phone/tablet/PC/web-server/firewall config/etc) in some way),

• MINOR version when you add functionality in a backwards-compatible manner (e.g. passing additional data to an already-provisioned API or adding any end-user functionality that does not affect the installation-requirements), and

• PATCH version when you make backwards-compatible bug fixes (e.g. fixing any end-user bug that does not affect the installation requirements).

By treating the installer-users as the consumers of an end-user application, and the installation-requirements as the public API, I believe that semver does make sense and is valuable as a communications mechanism for end-user applications.

https://medium.com/@u_glow/making-sense-of-semantic-versioning-for-end-user-software-applications-a3049d97478b

like image 93
Luan Kevin Ferreira Avatar answered Oct 22 '22 15:10

Luan Kevin Ferreira