How to run a composer package version?

I am starting to develop a package that I would like to open and use in future projects. I do not understand the right steps to get this started.

I just created a repository on github and here is my composer.json

{
    "name": "ProgrammingAreHard/Arbiter",
    "license": "MIT",
    "type": "library",
    "description": "Convenience library to manipulate Symfony ACL's",
    "authors": [
        {
            "name": "David Adams",
            "email": "adams.david.10@gmail.com"
        }
    ],
    "autoload": {
        "psr-0": {
            "ProgrammingAreHard\\Arbiter": "src/"
        }
    },
    "require": {
        "php": ">=5.3.3"
    },
    "require-dev": {
        "symfony/security": "2.4.*",
        "phpunit/phpunit": "~4.0"
    },
    "minimum-stability": "dev",
    "target-dir": "ProgrammingAreHard/Arbiter",
    "extra": {
        "branch-alias": {
            "dev-master": "1.0.x-dev"
        }
    }
}

I have a hard time wrapping my head around the version. I have not made any git tags. I branch-aliasonly put it because I heard that this is a good practice. I'm not sure if 1.0.x-devthis is what should be there right now.

What should I do at this moment? I am not in a situation where I like version 1.0. Should I create a lightweight or annotated git tag with something like "v0.1.0" immediately or wait until I am at the point where it is fully functional?

What should I do so that this is not a headache later?

, git (?)

+4
1

( , ), 2.0

(0.y.z) . .
API .

API , 0.x.y.

+3

Source: https://habr.com/ru/post/1538515/


All Articles