Hi,

Drupal 5 looks fun but since I'm not good in web technology I have to wait until all modules are stable before I can risk to move because in case the upgrade fails I might have a big problem. Other than issues I don't have important modules. Maybe you can tell me how long approximately I have to wait, I don't want to hurry you, I just like playing/working with the latest and greatest applications, if it's not ready, I'm gonna wait patiently.

thx

stax

my site

Comments

dww’s picture

dww
we/he/they
commented

yeah, sorry, i'm on vacation until the end of february, and won´t be able to work on fixing the upgrade proceedure for project* until after that.

revival’s picture

revival commented

Yes, would be great...

Thanks for the module...

aaaaaabsssssgu’s picture

aaaaaabsssssgu commented
Version: 5.x-0.1-beta » 5.x-0.2-beta

I took the risk updating, no problem at all here!

dww’s picture

dww
we/he/they
commented

right, the only real killer for the 4.7.x-1.* to 5.x (or 4.7.x-2.*) upgrade path is if you had defined releases in the old system. if you're using project* without releases, there's nothing really to worry about for upgrading to 5.x.
cheers,
-derek

seanbfuller’s picture

seanbfuller commented

I also updated with minimal problems. I had to restructure my taxonomy a bit, but otherwise there were only a few minor issue. I had something like this:

client 1
client 2
client 3
client 4
etc.

And had to create something like this instead:

active
-client 1
- client 2
inactive
- client 3
- client 4

I also found that I had to edit each project through the interface to get the new taxonomy association. Otherwise, things weren't showing up correctly in the project listing or in the issue queue. Hope that helps someone.

hunmonk’s picture

hunmonk commented
Status: Active » Closed (fixed)