search

thephpleague / tactician-bernard

Tactician integration with the Bernard queueing library
MIT License
19 stars 3 forks source link

Up the tactician version to .5 #23

Closed rtuin closed 9 years ago

rtuin commented 9 years ago

As far as I can tell no changes from 0.4 to 0.5 of tactician have impact on how the bernard integration at this time. So it is safe to upgrade.

sagikazarmark commented 9 years ago

Thanks. I am thinking about if we could allow both 0.4 and 0.5, since the changes in 0.5 has no effect on the bernard plugin. What do you think?

On the other hand, until 1.0 we should force people to use the latest version to make sure they are getting closer to the stable.

/cc @rosstuck

rosstuck commented 9 years ago

I would prefer a bump to 0.5, just to have fewer edge cases to consider right now. If you'd prefer to change the constraint to keep 0.4 viable, that's fine too.

sagikazarmark commented 9 years ago

Actually I don't prefer it, just thought about it. @rtuin thanks again.

rtuin commented 9 years ago

Good thinking guys. What do you think about keeping this repo's versioning tied to tacticians version numbers for minor releases (and <1.0)? Just like Symfony2 does with its components.

Op 6 apr. 2015 om 13:49 heeft Márk Sági-Kazár notifications@github.com het volgende geschreven:

Merged #23.

— Reply to this email directly or view it on GitHub.

sagikazarmark commented 9 years ago

I don't really like the idea. Since this plugin relies on third-party packages, we should be able to follow its changes.

rosstuck commented 9 years ago

Agreed, also keeping it in sync across all the packages leading up to 0.1 would lead me to tears. :sob:

When we hit Tactician 1.0 though, we should probably consider marking some of the packages then as stable but on a case-by-case basis, especially for those with third party integrations (the far side may not be stable yet)