A simple, but great module!

This is the only issue i have. I tested earlier 5 dev versions already.

Is there any plan releasing (soon) an official 5.x.1.x version of 'me' aliases?

I also tried integration with pathauto + globalredirect. On the first glance it seems to integrate smoothly. No issues for this now. I wouldn't use me-aliases if I can't use it with pathauto and globalredirect. These both are more important to me.

Comments

ahoeben’s picture

Any reason in specific the 'dev' version is not good enough? What would an 'official' release give you that you don't currently have?

sepeck’s picture

Branching to a 'release' will allow the update module to properly monitor the status. While this module is currently in contrib, elements of it will b emigrating to core for Drupal 6

http://drupal.org/project/update_status

A. The update status module only has knowledge of official releases. Official releases have names that look like this: 5.x-1.0. The update status module does not track the update times of development versions of modules, whose version numbers are in the form of 5.x-1.x-dev. Update status also does not know the status of any module that was not installed via a tarball produced by drupal.org; thus it doesn't know about modules you installed via a CVS checkout, nor custom modules that are not hosted here. See the handbook page on version info for more details.

Not to mention from a user point of view, using something marked 'dev' in production doesn't have that nice, comfortable ring to it. :D

ahoeben’s picture

Version: 5.x-1.x-dev » 5.x-1.0
Status: Active » Fixed

Point taken (the first reason, not the second)

Anonymous’s picture

Status: Fixed » Closed (fixed)
schnizZzla’s picture

with dev releases, it's not hard to check if updates have been made. Also this means marking your code as stable. This encourages people using it on live sites.

schnizZzla’s picture

typo: it's hard to check ...