Problem/Motivation

Even it's an young module, maybe there was enough time for this one run in productions.
If there is not known issues, imho, it should have a "most stable" release, maybe a RC release or at least a beta.
The people maybe we'll avoid to use this module, as they keep see alpha version for a while ...

Steps to reproduce

Proposed resolution

Make a new "more stable" release, even there are no changes, to indicate it's stable enough to be used in production.
Maybe also mention if there are known issue, and it could and should be used in production.

If it's not ready yet, then update the issues and create the new issues are needed for a new stable release.

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork revision_manager-3554605

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

vasike created an issue. See original summary.

j-barnes made their first commit to this issue’s fork.

j-barnes’s picture

j-barnes commented

@vasike - Makes sense to me, we have a good bit of test coverage now too. Tagging a beta.

j-barnes’s picture

j-barnes commented
Status: Active » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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