Etiquette: bump version of my open source fork project?

This question is about etiquette and open source projects.

I forked the app from github and added two new features.

  • the first function was often requested elsewhere. I added. The code and implementation are clean (I think).

  • the second function is rather a hack. It will be useful to others, but the implementation is a bit dirty in use and, moreover, in the code. I need a function, but I do not have the skills to fully implement it properly or to a level that can be considered worthy, while this contradicts the main project.

How to work with versions? Can I just update the version numbers without worries and click on my main branch?

It is annoying to know which version is working, modified or original, since both have the same version number. But will it be confusing when after a few months my github page will have a version number that is the same as the original, but both are completely different. (I made download requests, etc., but that doesn't concern my question.)

The project that I used forked uses a ruby ​​jeweler, so it has a version format:

The jeweler tracks the version of your project. It is assumed that you will use the xyz version

x is the "major" version, y is the "minor" version, and z is the patch version.

Is this standard for other projects / langauges too? Are my changes hotfix?

thank

+5
source share
3

. . ? - , ( , , , ), , .

1.2.3-ross, .

, , .

+4

, , - ( ).

? (, , .)

, , ? , , .

? , - - , , .

+1

fork, , .

Otherwise, a version number is usually used, indicating that the branch and the set of changes are triggered by ala -git-ross-12345

+1
source

All Articles