Tag a 1.3 release about php-resque HOT 13 CLOSED

As a followup - I guess a 1.2.x release would be better as the current version of php-resque-scheduler specifies "chrisboulton/php-resque": "< 1.3" as a requirement :)

from php-resque.

+1

from php-resque.

+1

from php-resque.

+1

from php-resque.

The problem with tagging a new release at this point is that there are a number of changes since 1.2 that are largely backward-incompatible with 1.2 itself (precluding the 1.2.x release), and still a few steps left in the 1.3 promised features set (preventing it from being tagged now as well).

Of course, that said, it might be possible to build a branch with only those changes that are not backward-incompatible with 1.2, thus allowing a 1.2.x release until the full 1.3 feature set is in place. But that can be a complicated process, depending on how those changes were introduced in the first place, so someone will have to spend some time making sure the branch is properly clean of the incompatibilities.

That time may be better spent building out the missing features from 1.3 and getting it out instead.

from php-resque.

+1

from php-resque.

Where is the 1.3 feature list? There aren't any milestones in the issue tracker here.

from php-resque.

Good question. @chrisboulton?

from php-resque.

We should really create a new version (maybe with #150 fixed). Other projects are also depending on PHP-Resque and want to stick to a specific version (semver.org).

from php-resque.

+1 It is a while since the last tag and other libraries can not easily depend on new features without risking some breaks when depending on master branch

from php-resque.

+1

from php-resque.

+1
Don't want to use code that has atrophied for 2.5 years, but would also prefer to not ride the dev tip. Composer/Satis can mark a particular changeset, but it is much better for the maintainer to tag the changeset than to choose something arbitrary.

While it may not be a sexy new feature, the project management work is just as helpful!

from php-resque.

See #274

from php-resque.