Alex,

A suggestion I've been meaning to make:

Could you please sequentially number or letter the archives for download? Maybe consider them "patch levels" if not really "new" "releases"

What most sites do where there are frequent releases is have a "current.tar.gz" file or link as well as the current version. It really helps keep things organized, and prevents overwriting a file with a version that doesn't quite work for your situation.

This way a quick look at the download zip will tell if you have the most current, or if you just want the most current you can click that link, and after download you can still roll back to the older version if you have to.

PUGDOG®
PUGDOG® Enterprises, Inc.
FAQ: http://postcards.com/FAQ

I echo this request...it is really problematic to keep track of "current", "previous", and "patches".

Regards,

Eliot Lee

One more request.

In the updates and change log, a better description of what really changed would be helpful.

In otherwords:

Changes to Database: (list of changed, added or deleted tables)
Changes to user files: (list of files changed in the public files area)
Changes to templates: (list of changes to templates
Changes to admin files: (list of changes to the files in the admin directory)
Changes to library files: (list of changes to files in the libraries.)

And, within those, the changes should be listed -- which line of the official release and/or what subroutine. It would also be nice to have a list of the changes between minor versions (ie: to the patches) in the headers of each of the files, so a quick look will tell if the file has been modified.

This may seem like extra work, and it is, but this program is immensely complex, and so are sites built upon it.

What would probably suffice is the "diff" file, run between the list of changed files (which is _very_ important in and of itself) and the offical last _release_version_. It would be nice to have a diff between the last patch version and the current one too, but that would require someone to check each release level individually to make sure all the patches were applied.

It's much easier on your end to track the differences between releases, than for each site to try to figure it out each time.

PUGDOG®
PUGDOG® Enterprises, Inc.
FAQ: http://postcards.com/FAQ

Hi,

We will be incrementing each release now, and I've added a ChangeLog.diff file which has a diff between each version.

Cheers,

Alex

--
Gossamer Threads Inc.