Support for 3.0 hacks
 

I wasn't around when vb2 went to vb3 so I'm just curious what other coders actions were with respect to supporting their older version hacks ?

I no longer run a vb 3.0 forum so from now until the end of 2005 I intend to only provide limited support for my old 3.0 hacks - which means no bugs will get fixed (assuming any exist) and no new functionality will get added. I will try and answer questions from people if it's possible without referring to any 3.0 code.

From 2006 onwards (by which time 3.5 will have been around 6 months) I will no longer officially support any of my 3.0 hacks, which means I will untick the supported option and no longer check the threads with any regularity (unsubscribe from them). That doesn't mean I will refuse to answer questions, but it will be a very limited and ad-hoc thing.

It may seem a bit harsh, but when you have limited time and don't get paid, you cannot fully support old stuff forever - what do others intend to do ?

I have a lot of old stuff released that I havn't supported in some time. After I stop using the version the code was written for I tend to stop supporting it. Most of it is lack of time and the fact that I don't have that version running anywhere anymore.

I was wondering the same thing Paul. I started putting up a note in the first post stating that I cant support them anymore because I dont run that version.

True, I could run a localhost test bed, but it gets messy and complicated. Ill help where I can, but its just too dificult to do when youre on another version.

Most people seem pretty cool about it.