Open ek9 opened 7 years ago
@richardmiller @pocky To illustrate this better I have made a test repository: https://github.com/ek9/behatspec-test It has 2 branches:
master
branch - using dev-master
of BehatSpec, which works fine (except issue #41 ). I've managed to test all the extensions when I was verifying the updated docs in #35 PR.v0.5
https://github.com/ek9/behatspec-test/tree/v0.5 - using ^0.5
of BehatSpec, which does NOT work due to bad PSR. The output of bin/behat
is:
[Behat\Testwork\ServiceContainer\Exception\ExtensionInitializationException]
RMiller\BehatSpec\Extension\BehatSpecExtension\BehatExtension
extension file or class could not be located.
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.
Currently due to bad namespaces the versions
0.4.0
,0.4.1
and0.5.0
are unusuable and in a bad state.I would suggest to release what we currently have as
0.6.0
and remove the0.4.0
,0.4.1
and0.5.0
as those versions will cause problems and shouldn't be used. Updating to0.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
:The setting above will make master branch an alias of
0.6.x-dev
. This way, anyone wanting to get master changes (after0.6.0
is released), can point to0.6.x-dev
instead ofdev-master
. No specific branches need to be created and we would keep usingmaster
.`