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

Cleanup non-working versions (0.4.0, 0.4.1, 0.5.0) + release 0.6.0 / 0.6.x-dev #32

Open
ek9 opened this issue Feb 19, 2017 · 1 comment

Comments

@ek9
Copy link
Contributor

ek9 commented Feb 19, 2017

Currently due to bad namespaces the versions 0.4.0, 0.4.1 and 0.5.0 are unusuable and in a bad state.

I would suggest to release what we currently have as 0.6.0 and remove the 0.4.0, 0.4.1 and 0.5.0 as those versions will cause problems and shouldn't be used. Updating to 0.5.1 wouldn't make sense as we have updated the namespaces and it warants a bump in minor version number.

I would also suggest at the same time to add this to composer.json:

    "extra": {                                                                                                                                                            
        "branch-alias": {                                                                                                                                                 
            "dev-master": "0.6.x-dev"                                                                                                                                     
        }                                                                                                                                                                 
    }                    

The setting above will make master branch an alias of 0.6.x-dev. This way, anyone wanting to get master changes (after 0.6.0 is released), can point to 0.6.x-dev instead of dev-master. No specific branches need to be created and we would keep using master.

`

@ek9
Copy link
Contributor Author

ek9 commented Mar 27, 2017

@richardmiller @pocky To illustrate this better I have made a test repository: https://github.com/ek9/behatspec-test
It has 2 branches:

None of the 0.5 series are usable. This has been fixed on master now by the PRs that were accepted. I suggest to merge #35 (which also fixes #41 ) and then release it as 0.6.0. The 0.4 and 0.5 should be untagged so no one uses them by accident.

This would really be final step after monorepo migration to have a tagged working version.

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