The project page already says "The active branch is 7.x-2.x." (far down at the end). I think it is important to make this much more visible so that users are focusing on testing and helping out with that version, and not downloading the 1.0 beta version.

When I went through all the open issues, see #1241564: [meta] Proposal for features needed for a full 2.0 release of the Media module, there where a lot of activity around the 1.x branch. I think it would be great if we can get those users to move the 2.x instead.

Another question needing an answer is if there even is a need for a 1.0 release?

Comments

dddave’s picture

dddave CreditAttribution: dddave commented

How much of my site gets lost when I change to 2.x dev? I guess there is no upgrade path and I would have to manually restore my old stuff?

I am using Media on my private blog/test site so I am very willing to test the heck out of it...but I am not that eager to work on dozens of nodes to repair them.

tsvenson’s picture

tsvenson CreditAttribution: tsvenson commented

@dddave: To be honest, I have no idea if upgrading from 1.x to 2.x is supported or not. The only thing I noticed when testing 2.x is that it seems to have pretty much the same feature set and UI's that the 1.x version I tried some months ago have.

Best advice I can give you is to simply use the Backup and Migrate module to take a snapshot of your live site and test what happens on a copy of it. Should be fairly quick to do.

Looking at the Usage statistics, only 262 out of 8,578 (almost 7.k on 1.0 b4 or b5)are using 2.x. So its a very small number on 2.x yet.

Maybe I should rewrite my question regarding a 1.0 version as:

What's the best option for the 1.x branch:
1 - Make a full 1.0 release
2 - Focus on creating an upgrade path from 1.0-beta5 to 2.x

Personally I think we have most to gain going for option 2 and get everyone on 1.x upgraded to 2.x. My hunch is that it is probably much less work needed to create an upgrade path than maintaining two versions of this module.

aaron’s picture

aaron CreditAttribution: aaron commented

the update from 1.x to 2.x should go smoothly. i want to ensure that continues, so please post any issues when you find them!

tsvenson’s picture

tsvenson CreditAttribution: tsvenson commented

@aaron: Great, then the best way forward would be to focus all efforts on 2.x and make sure current 1.x can be upgraded to it?

I think it would be good if you and the other maintainers could make an official decision about this. Then everyone knows where the future is and they will have good reason to upgrade.

dddave’s picture

dddave CreditAttribution: dddave commented

Just for the record and to encourage everybody to check out the 2.x branch: The upgrade went supersmooth and everything seems to be running fine.

tsvenson’s picture

tsvenson CreditAttribution: tsvenson commented

@dddave: Brilliant news, at least we are up to 263 2.x users and one less 1.x then :)

Big thanks for testing and reporting this.

@aaron: Any chance we can get this information up on the project page?

dddave’s picture

dddave CreditAttribution: dddave commented

Upgrade went smoothly the hassle begins of course if you try to ditch the styles module which no longer is required. ;)

edit: Ok, ditching the styles module and trying to make my old posts look nice again is an usability nightmare. People upgrading should be very aware of this. I think I also discovered a couple of bugs...(reports coming).

fedbccer’s picture

fedbccer CreditAttribution: fedbccer commented

As suggested in this issue I started using "Media" with the 7.x-2.0-unstable1 version but I had to uninstall it and move to 7.x-1.0-beta5 because 7.x-2.0-unstable1 is incompatible with "Media Gallery" 7.x-1.0-beta6
I'll wait for a next release of Media Gallery before moving again to the 7.x-2.0 branch.

tsvenson’s picture

tsvenson CreditAttribution: tsvenson commented

@fedbccer: Sorry to hear that. However, would like to recommend that you avoid the Styles module if possible for 1.x. 2.x is moving to use the File Entity module instead and others have reported that it creates a bit of pain when upgrading from 1.x to 2.x.

fedbccer’s picture

fedbccer CreditAttribution: fedbccer commented

Thank you Thomas,
I just check, I have the CTools's Stylizer sub-module active but I don't have the Styles module installed, despite I have a "styles" folder in "sites/default/files".
At the moment I'm testing the following suite of Media related modules:

I still haven't the videos working: I need to study a little bit more how everything must be put together

tsvenson’s picture

tsvenson CreditAttribution: tsvenson commented

@fedbccer: the styles folder is for Drupal Core image styles. But now we are going off topic here. Please file a new issue if you keep having problems with this.

dlumberg’s picture

dlumberg CreditAttribution: dlumberg commented

sub

SeanBannister’s picture

SeanBannister CreditAttribution: SeanBannister commented

sub

hernani’s picture

hernani CreditAttribution: hernani commented

sub

mightyiam’s picture

mightyiam CreditAttribution: mightyiam commented

sub

rosborn’s picture

rosborn CreditAttribution: rosborn commented

sub

Dave Reid’s picture

Dave Reid
he/him
Primary language English
Location Nebraska USA
CreditAttribution: Dave Reid commented
Status: Active » Fixed

Yes, we still do need a 1.0 release which will be feature-locked and everything new is on 2.x. Users that just want a stable version without major changes will prefer that release.

Status: Fixed » Closed (fixed)

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

dlumberg’s picture

dlumberg CreditAttribution: dlumberg commented
Status: Closed (fixed) » Fixed

Just keeping this thread alive, I guess until the Code Sprint: http://groups.drupal.org/node/173749

/me shakes fist at System Message

Status: Fixed » Closed (fixed)

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