"you don't know or see all things"

That's the problem...   that is why many people want access to the code at all times to see what is going on.    What if you changed something that me or my customers don't want.... should I just throw out a new release and then wait for them to call and say hey where is this option or hey I have a new editor and now I have to train the people that update content.

If a thorn is asking what changed in a release and why is there a release done and questioning your reasoning for encouraging people to upgrade, well...   I wonder even more about the management of this process.

Brian, you don't have to upgrade to 4.5.3.

There are some issues, that will be clearified eventually, that 4.5.3 addresses. Like I said, they were important enough that they were done swiftly and a new release was packaged and made available.

:)

I'm waiting for 4.6, web service self install