Many bug fixes have been committed since the last release (7.x-3.0-alpha2), so I'm planning on rolling a new release. If any of my co-maintainers object, please say so.

Comments

kylebrowning’s picture

+1

jobeirne’s picture

Released 7.x-3.0, since we're fairly stable at this point.

jobeirne’s picture

Status: Active » Closed (fixed)
kylebrowning’s picture

Status: Closed (fixed) » Active

Id at least do a beta for and an rc before release.

Jumping from alpha to a release is generally not a good idea.

jobeirne’s picture

Shall we roll this back to a beta release? If so, what is our roadmap towards a major release?

kylebrowning’s picture

I would roll it back, but not sure how to do that., I havnt had time to come out with a plan yet, Ive been focusing on services 3.2 b/c it re adds support for oath settings per endpoint.

:/

jobeirne’s picture

No worries, I'll just delete the 7.x-3.0 tag and roll it back to a beta release.

jobeirne’s picture

Bummer! Tags/releases can't be deleted on d.o. I'll just move on to 7.x-3.1-beta1.

kylebrowning’s picture

Why are you gonna roll a release to stable when there is 10-14 bug reports on 7.x alone?

steinmb’s picture

Or simply to: Fix stuff and roll 7.x-3.0, there will always be bugs :) Kyle mention in #9:

Why are you gonna roll a release to stable when there is 10-14 bug reports on 7.x alone?

Any show stoppers here people should focus on?

steinmb’s picture

Status: Active » Fixed

7.x-3.1-beta1 out, let's just close this

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.