I'd like to be presented with an option when upgrading with Drush. The default is presently the old 7.x-1.0 when using drush and there is no explicit option to choose the better supported 7.x-2.0-alpha2. This module seems to be an exception in sticking with the less supported, but stable 7.x-1.0 release, rather than giving folks an option of moving up to the alpha2.

Comments

mgifford’s picture

mgifford
he/him
Primary language English
commented
Title: Expose 7.x-2.x-dev to Drush » Expose 7.x-2.0-alpha2 to Drush

I don't much care if it's the alpha or dev.. But the developers should expose one of the 2.x releases through Drush.

tstoeckler’s picture

tstoeckler
he/him
Primary language German
Location Essen, Germany
commented

What exactly do you propose?
The alpha2 is already markes as "Supported" on d.o.
I don't exactly know how Drush's pm suite works internally, but I didn't know that you can explicitly "expose" releases if not through d.o.

mgifford’s picture

mgifford
he/him
Primary language English
commented

I don't know enough about how drush does this. I think it's because it's not a "Recommended release" but rather a "Other release". Not sure how drush manages that.

robloach’s picture

robloach
he/him
commented
Status: Active » Needs review

drush dl libraries-7.x-2.x ? Just having drush dl libraries will get the latest stable release. alpha isn't quite stable, but I'd consider it pretty close!

tstoeckler’s picture

tstoeckler
he/him
Primary language German
Location Essen, Germany
commented
Status: Needs review » Active

How about this:

tobias@euve23100:~$ drush rl libraries
------- RELEASES FOR 'LIBRARIES' PROJECT -------
 Release         Date         Status
 7.x-2.x-dev     2011-Dec-15  Development
 7.x-2.0-alpha2  2011-Dec-15  Supported
 7.x-1.x-dev     2011-Feb-25  Development
 7.x-1.0         2011-Jan-27  Supported, Recommended

tobias@euve23100:~$ drush dl libraries-7.x-2.0-alpha2
Project libraries (7.x-2.0-alpha2) downloaded to                     [success]
/var/aegir/libraries.

??

Is there anything we need to do here?

mgifford’s picture

mgifford
he/him
Primary language English
commented

Yes, this has always worked.

But it is an exception to have to specify the version number. Generally, and I've updated a lot of modules through Drush, you are either given an option of releases to choose from if there is a need to choose.

Running:
$ drush dl libraries

Shouldn't just automatically overwrite whatever's in the library with the older 7.x-1.0 version.

Because other "stable" releases are built off of the Libraries very stable alpha2 we've had to go back and find the full library name for the alpha code several times to resolve errors that have popped up in other modules due to an inadvertent downgrade in libraries version.

If Drush simply presented an option of choosing version 1 or 2 of the code base then this wouldn't be an issue.

Maybe it's just easiest to call for alpha2 to be released as stable.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

Running:
$ drush dl libraries

Shouldn't just automatically overwrite whatever's in the library with the older 7.x-1.0 version.

That's a bug in drush, cannot be resolved here. (Projects should never be downgraded without confirmation)

If Drush simply presented an option of choosing version 1 or 2 of the code base then this wouldn't be an issue.

If I'm not mistaken, then drush only asks for the release to download if there is no recommended major version.

While we could unset/remove the recommend major version setting for Libraries, this would make it slightly harder for people to download the current 1.x official stable.

Maybe it's just easiest to call for alpha2 to be released as stable.

I don't think we're there yet. I once initiated work on an advanced implementation in http://drupal.org/project/jquery (involving a libraries handling complexity for which 2.x was mainly designed for) and we improved the API based on that, but didn't have time to work further on that (to test and validate the API changes).

Of course, plain detection and loading of libraries should work - just like it works in 1.x - but that's not really the purpose of 2.x. ;)

robloach’s picture

robloach
he/him
commented

I don't think we're there yet. I once initiated work on an advanced implementation in http://drupal.org/project/jquery (involving a libraries handling complexity for which 2.x was mainly designed for) and we improved the API based on that, but didn't have time to work further on that (to test and validate the API changes).

Although not really in scope for this issue, I have quite the patch up and running for this :-) .

mgifford’s picture

mgifford
he/him
Primary language English
commented

I added this bug issue for Drush #1392920: Projects should never be downgraded without confirmation

That might be the best we can do for this for now. Quite interesting about the jQuery library btw..

tstoeckler’s picture

tstoeckler
he/him
Primary language German
Location Essen, Germany
commented
Status: Active » Closed (won't fix)

Closing this for now.
Please re-open if there is anything we can do over here.