Shouldn't you roll the code base # when you modify it? So 3.4.0.XX, where XX changes every time you update something. The "0" or minor revision change could be tied to your normal point updates so that can stay the same. If not how does someone tell (other than to read the forums or log into the ACP while you leave the notice up for a few days) that a security or other code change has happened?

Isn't this standard practice? Seems to be something you can fix. Simply updating the code in the download area for minor changes gives zero sign that it was changed and is not the same as the identical software version posted prior.

bump...

We've been asking for a release date or revision number or something of the sort for a long time. :ermm:

And we all despair that such standard practices like this will ever be implemented. :cry:

Maybe things will change with 4.0.0? Seems they're already planning out a smoother, quicker upgrade process so it's not impossible.

It seems this thread is being ignored too. While not what I would want to hear, a simply "no" would be appreciated if that is the answer.

We've read the thread. It's not "being ignored". We do not reply to every topic started in the forums, even if we read every one (as has been stated many times in the past).

I guess the problem is that if something is suggested over and over, then perhaps it's something IPS should start to consider :)

We've read the thread. It's not "being ignored". We do not reply to every topic started in the forums, even if we read every one (as has been stated many times in the past).

Since you have seen it many times what is your reply? Yes or no? It is the most simple of questions. I'm not trying to be rude but your answer was basically "we read it and it was not important enough to reply to". I know you guys are busy and thank you for working hard on code instead of replying on the forums all day, but when we ask you something directly I hope you can reply when there is time.