What needs to be done to make 7.x-2.x a stable (and recommended) release [#1942744]

I have been using 7.x-2.x for a very long time and have never had any issues with it.

On the other hand, before I switched over to it, I almost always had problems with the 7.x-1.x version, mainly that it would refresh the whole page when changing tabs and you would lose your previous selections.

What is holding 7.x-2.x back from being a stable and recommended release?

Are there some issues that are considered blockers?
If so can we list them, if not can we make a 2.x stable, recommended release?

Comments

Comment #1

Chris Charlton

English

Los Angeles

CreditAttribution: Chris Charlton commented 3 September 2013 at 23:13

+1 to this question.

Also, is there a clear separation between the two versions? If so, would you mind adding a note to the project page explaining who/why each version should be used.

Comment #2

rooby CreditAttribution: rooby commented 4 September 2013 at 00:24

The difference is basically that the new version is an evolution of the old one.

The user interface has been greatly improved and some bugs have been fixed.

There are possibly other things that don't concern me, but those are the things that mean I always use 2.x.

It's not buggy and you can easily switch between 1.x & 2.x so you should try 2.x if you haven't. You won't look back.

Comment #3

Chris Charlton

English

Los Angeles

CreditAttribution: Chris Charlton commented 12 September 2013 at 17:43

Okay. Then it makes sense to ask if there is any reason to continue developing/supporting the 1.x branch? If not, or at least not forever, consider generating an "RC" or "Beta" supported tag for 2.x.

And, one request: It'd help adding your tidbit about the difference between the two versions for people to start adopting the 2.x branch more. I'm sure most people are only grabbing 1.x because it's marked as supported versus the dev branch, and Drush is defaulting to that version as well because of the tagging.

Comment #4

rooby CreditAttribution: rooby commented 12 September 2013 at 22:47

All we really need is to make a release of 2.x and make it the recommended release, with a note about what has changed.

It's possible the bugs in 1.x that I was referring to are fixed now I'm not sure, but they were around when I switched to 2.x, which was well over a year ago.

Comment #5

Chris Charlton

English

Los Angeles

CreditAttribution: Chris Charlton commented 22 October 2013 at 22:20

If that's the case for 2.x-dev now, I suggest tagging a release. I'll take anything: 2.0-alpha1, 2.0-beta1, or 2.0-rc1 if nothing else suggests how close the build is.