Contributors ... Please Update Users

**ideasgirl** · 28 Oct 2006, 04:21 AM

We all want to be up to date with ZC new version, we all want all the bugs fixed, security holes correctly applied, and use the new features; but we also don't want to upgrade guessing or hoping a module we are used to, is going to work.

Please, let us know in your own support thread/s if your module or template is compatible with the new version, and if it's not, if an upgrade is going to be released or not. That way we know in what direction we are going when we are upgrading.

Posting something like:
Compatibility with ZCv1.3.6 = Yes or No
Upgrade will be Released = Yes or No
Expected Day to be Available = Submitted and Waiting Approval, 3 days, 1 week, or whatever it takes...

This should be done each time a new version is released.

Your consideration on this matter will make everyone happier.

**swguy** · 28 Oct 2006, 09:10 PM

This is a worthy suggestion ... but remember contributors are hustling to catch up just like you are. We don't get any advance notice that a release is coming down the pike! :)

Best practice: update in a sandbox cart and test test test. If you do find problems, notify a contributor asap so that effort is not duplicated.

Thanks,
Scott

**ideasgirl** · 29 Oct 2006, 07:35 PM

I do understand your point, but isn't the developer the best to know this? Who best know the details of the code, how it works, what files are edited, added, or used with their module?

Yes, I can compare files... but what difference will make if I don't know that taking out that comma from there, or adding a "." over there, will make the difference?

I'm not asking for instant upgrade, to drop everything and start working on it. I just want a light on the road to know where I am or at least read a map. A simple "won't work because... " or "I don't think there will be issues with new release because..."; that way we know what are our chances and risks, and if we want to take them.

**swguy** · 29 Oct 2006, 07:41 PM

When I said, "test, test, test" what I meant was test, not compare code files.
I certainly would not expect to have the average contrib user mailing me
code suggestions (although oddly enough, it does happen occasionally).

Scott

**Vger** · 30 Oct 2006, 07:30 PM

It's not so easy, for some of the reasons given.

1. Developers get no advance notice
2. Updates can be BIG or small
3. Updating a contrib to only work with a newer version of Zen Cart may break it if people try to install it on an older version.

Vger