WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!! WE NEED A CHANGE LOG!!!

I hope i've made my point clear. i don't see what the point is of releasing new versions if you don't even tell us what's new about them. you have to justify to me why i should spend the half hour downloading the new files on my shared 56k connection if you want me to upgrade. one great thing about the new version information in the connections window is that you can see NO ONE UPGRADES!!! if you really are trying to "improve the health of the network" and add new features, you have to get people to download the new versions and use them, and they won't unless they know what's so great about them.

I AGREE, well I think that Everyone agree even if it says "small bugfixes"

i don't know why there isn't one. i can't think of one good reason to keep people in the dark and many many good reasons to keep them informed. how hard would it be to make a list of everything that's been done since the last version!!! i'm sure there's already one in use internally somewhere.

Good version control is harder than it sounds. I'd rather the developers spent their time (and my money) writing LimeWire than writing change logs.

And if you really want to see what has changed, you could download the source and run a diff between versions.

Of course, if they had the resources of M$, I'd be very pleased to see a properly maintained change log...

Mark

Great idea to download the source and compare versions...
Maybe for you Mark but what dummies like me who are not techies?

I'm just a LW Pro USER and I would bet that most LW users are not into code analysis.
I wouldn't know a good or bad source code if it bit me in the rearend.
And, I will likely always be just a USER of all the programs I have on my old Mac.

I am just looking for, an easy to understand listing, in a few simple words,
what each new LW version is ADDING or IMPROVING or FIXING or TAKING AWAY.
And, it also would be nice to know if the "changes" are for ALL operating systems.

I agree with Rhohl, how can the developers NOT know what they're working on or what's been finished. They have a TO-DO list which i saw once, and they cross things off of the list whenever it's done, so how hard would it be to convert that into a change log?
Also, treatid, you're working under the impression that "the developers" are one group. They're not. There's a group of 3-4 "official" limewire developers, but there's also tons of other individuals who participate and help code. The only way they can keep all this organized is with "good version control" so that work doesn't get reproduced & code can be checked. I know it's out there, they just have to make it available to the public, and as i've said before, there's no good reason why they don't.

On Tuesday May 14th, I received the following email from LW:

"....This is a notice to Windows LimeWire Pro users who updated their
LimeWire over the weekend of May 10 to May 12. If you are using
LimeWire on a non-Windows operating system, this problem did not
affect you, and we apologize for bothering you with this message.

Over the above mentioned weekend, there was a bug in the automatic
updater for LimeWire that may have disabled your LimeWire system,
making it impossible to start the program a second time after
performing the update. We sincerely apologize for causing this
error. Fortunately, however, a fresh reinstall of LimeWire will
get it back up and running normally....."

In other words(?) LW 2.4.4 is the same(?) as LW 2.4.3 except for the
"Windows LW Pro users" but with a specific bug fix...

How many other LW versions have been released for similar reasons?

And, wouldn't a little version information on the download page help?
(especially for those who follow every incremental change)
There was no mention of this bug fix on my download page for LW 2.4.4

I quite agree. A list of changes of the latest version on the LW update page would help me decide whether it's worth downloading:

They've introduced file hashing and dynamic resume? Yes I'll download it!

They've fixed a bug that doesn't affect me and made a couple of cosmetic changes as an excuse to push the version number up? No, I don't think I'll bother.

They should also include a full version history with the installer like in most other commercial and shareware software.

Paying Pro users have a right to be informed in detail about development of the product we are helping to finance. At the moment to get [some of] this inforamation, you have to spend a lot of time trawling through forum posts or study the Gnutella and LW developer pages (if you're a programmer, which I'm not).

I still haven't heard any good reasons why there isn't a change log. It seems everyone agrees that one is needed and the only counter-argument is that it'd be too hard to do (it's not). Does anyone have a reason this isn't a "feature" of limewire? Any reason at all. If I hear a good reason why there shouldn't be a change log, i'll be satisfied and drop the subject, but i'm still waiting.....

This thread has been going for a week with several opinions that mostly seem to agree about something that would be very easy to implement (I recognise that many requests are unrealistic, though not this one). However, there's been no response from the LW developers. Why not?

I would like to conclude that they're all too busy writing the full version history and perfecting the major updates that are going to appear in LW 2.5 and that will make me say to myself "Gosh! I AM glad I paid for LW Pro!"