Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move from tag based versioning to branch based versioning #7

Closed
Southclaws opened this issue Jun 16, 2018 · 0 comments
Closed

Move from tag based versioning to branch based versioning #7

Southclaws opened this issue Jun 16, 2018 · 0 comments

Comments

@Southclaws
Copy link
Collaborator

Currently, sampctl users use tags to specify versions:

sampctl/samp-stdlib:0.3.7-R2-1-1

Which works for linear changes. However, a lot of the team want to start experimenting with minor improvements such as missing functions and fixes to certain definitions. This would be easier if split onto a separate branch but doing this with 0.3.DL support is difficult.

So I propose moving from tags to branches, so 0.3.7 could be specified with:

sampctl/samp-stdli@0.3.7-R2-1-1

While keeping master branch the "latest stable" (0.3.7) and maybe opening up "experimental" branches from these base branches for new things like adding native IsValidVehicle(vehicleid); etc.

Another reason for this would be to avoid breaking scripts that already include things such as the IsValidVehicle declaration etc.

I'd like to have some feedback from the sampctl community regarding this as changes to this repository will basically ripple to every project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant