Can you please make an "offical" release for 5.x?
Thanks!
Jen

Comments

jenlampton’s picture

any progress on this? Can I help?

Riccardo83’s picture

doesnt seem anything is happening, any alternative guys?

doc2@drupalfr.org’s picture

So, there's been a new .dev release announced today by my update_status.module, on February, 11th 2008. Check the video.module releases.

but I don't know what this release fixes/commits..? As I already patched my video.module a few times, I fear to loose my changes with this new undefinite version. Fabio, or anybody else who contributed or examined the code, could you please tell us what's been implemented? I guess #68917: Add support for .avi and .mpg videos is in the box, but only guessing right now!

Thus we could also give you feedbacks about your changes.

Thank you. Regards, Arsène

fax8’s picture

the new development version is the result of a complete rewrite I did. It's still development code so you shouldn't use this on a production environment. Moreover we currently have a bug which let any old video node unplayable after the upgrade to the new dev version (see http://drupal.org/node/220929).

I and Vernon decided to commit this code as we are trying to get help from the community to make the code stable and ready to realease a stable version.

So.. If you are using an old -dev version of the video module and you are using it on production without problems you should continue staying with it.

Instead if you want to help in developing/troubleshooting the new version just use the new code.

Fabio

fax8’s picture

In order to see the new features I suggest to install the new code on a testing drupal install created from scratch.

You will see that there are radical changes in the UI, featueres, apis and lot more. I think this is a good step forward for the video module.. but as there is lot of new code it might require time to get a good level of stability.

doc2@drupalfr.org’s picture

Thank you for those valuable infos Fabio, and for the work you've done with Vernon.

Personaly, and I regret this, I probably won't have time to test this new version, unless it gets the kind of stability just as fast as the previous version acquired in a few months only (thanks again for that).

Thank you for the follow up in #4. This is a very concerning issue for the numerous users of the video.module.

Some suggestions:

1- In order not to get flooded by 'old video node unplayable' issues, you should put these #4 (and eventually #5) informations into the project page, or at least in the releases one.

2- To prevent urged updaters from asking where to find the previous version, I think you should give a link to the previous version of the module, renamed to its release date eventually.

3- Better, you should even give your 2 versions 2 different names so that the previous issues (with their patches and code snippets which, in the end, answered many/the main problems for production environments) don't get messed up with issues related to the current new "2008" version. Why not having a 5.x-2.x-dev version for this current "2008" new release, since the code has undergone a complete rewrite.

    The fact that there hasn't been a stable 5.x-1.0 version in 2007 (an before or in early 2008) should not be a problem as long as it's clear on the project page, imho.
    Else, I don't know if it's possible to have something like version 5.x-1.1.x-dev for this new version. It might only be pertinent if you plan to solve the #4 bug, not if you don't.

Arsène

jenlampton’s picture

I agree wholeheartedly about giving the completely different versions of the module, at least, different release numbers. It would also be nice for those of us running a quazi-stable version from last year to still be able to download that version from this page, until the new version is usable.

Here are some basics about branches and tags for releases of your module: http://drupal.org/handbook/cvs/branches-and-tags/contributions

Jen

hypertext200’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

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