By mactoph on

I mistakenly installed the CVS version of the Category module ( http://drupal.org/node/39683/release ) instead of the stable version. I am worried that this may cause problems when I eventually update to the stable version. They were both last updated on the same day, so I am not sure that I even need to worry about it?!?
If I may run into problems with the CVS version, any recommendations on how I can revert to the stable release?

Comments

bugz_nz’s picture

bugz_nz commented

The CVS version is not necessarily unstable and may contain features that are intended for the next stable release. If the module is working with no ill effects, then you might as well keep it installed.

If you have any worries, follow the bug trackers for the modules and keep an eye on any issues that people post against the CVS version that may affect you.

bjornarneson’s picture

bjornarneson commented

If there are database updates to be performed with an upgrade to CVS (or a higher stable version number), be aware that it might be difficult to "downgrade" once you've performed those updates.

I have no idea if category.module even uses database tables, but this should be a general FYI to anyone considering walking on the "bleeding edge" with any module (or even Drupal core).

bugz_nz’s picture

bugz_nz commented

To follow on from that - Anybody walking on the "bleeding edge" should be doing so in a test environment. It's not a good idea to install contributed modules directly into your production site, without some sort of testing.

This will prevent a lot of heartache if something breaks.

mactoph’s picture

mactoph commented

I received an email directly from Jaza, the developer of the Category module and he let me know that in this case the stable version and the cvs version are exactly the same.
Thanks for the help on understanding how the CVS modules generally compare to the stable releases-