When using drush make it is easy to target a particular git commit, but for site builders, they are more likely to rely on using releases for their builds. Nightly snapshots are always changing and so are a moving target for site builders. I think it would be a good idea to release a proper release, even if it is an alpha or beta.

Comments

SebCorbin’s picture

Priority: Normal » Major

I use this module in production with no issue, a proper release (even alpha or beta) is required to start translating it via localize. Please add one :)

james.williams’s picture

Assigned: Unassigned »

Ivan, I think you're the only one with permission to create releases at the moment?

An alpha version would be a good idea. I haven't had time to do any maintenance work on the project recently, but there are several patches in the issue queue that could do with being applied at some point - I'd wanted to get them applied before asking for a release really, but I think time has just moved on too much to hold back any longer.

Anonymous’s picture

I try to make some time to go through issues.

jay.lee.bio’s picture

I'm also anxiously waiting for an alpha release. :)

Bram Rongen’s picture

The module seems to be going through major revisions, any plan of releasing an alpha soon?

mrharolda’s picture

We like to use this module for a client, but we have a (non-strict) policy not to use -dev modules. Can we help to get this module to an alpha stage?

Anonymous’s picture

Contact noels or PawelR. I gave them access and they are the last devs to commit some code, so currently they have the best knowledge of the module's status.

nancydru’s picture

IMHO, once #1605242: Pass coder review is fixed, an alpha1 release would be appropriate. There are many more fixes to be done before a stable release would be ready.

pameeela’s picture

Assigned: » larowlan
Issue summary: View changes
Status: Active » Needs work

Looking at an alpha2 release as soon as blockers are sorted.

larowlan’s picture