Is it just me or does anyone else also think ips are not sticking to what they believe in
I recall they used to say that 'we will not release a product until it has been tested as not good practice to release something and then a few days later have to release updates etc' ... or at least words to that effect ??
So what happens .. they release Blog 1.4.0 and then 6 days later release Blog 1.4.1
What is the game here ips
Customers install 1.4.0 and skin it and everything to their requirements and what happens ... ips release 1.4.1 ... 6 days later so you have to add/make the changes to your skins etc (where required)
Why have you changed from 'we will not release a product until it has been tested as not good practice to release something and then a few days later have to release updates etc' ??
Admitted it is better to get the 'fixes' released but should it not have been tested thoroughy before releasing 1.4.0 in first place otherwise you are not practicing what you preach and going against what you state, if it had been tested before being released then 1.4.1 would not have been needed yet
perhaps change the meaning of ips to invision patching services
thats just my thoughts on this.
Full Version: Why updates released so soon after previous version ?
QUOTE (steve777 @ Jun 28 2008, 11:23 AM) 
they release Blog 1.4.0 and then 6 days later release Blog 1.4.1
^^ ?? (itīs about one month, isnīt it...)
well, i appreciate the patch update!
Yeah it was a month
Personally, I'd much rather get 6 patches spaced a day apart, than go a month with what may be a vulnerability (or even a simple bug) in the software before I get 1 patch that covers it all. Only my opinion, of course...
Where did he get 6 days from lol? Did you even bother reading the announcements to view the actual release dates of versions? Many of us keep up with the bugtracker to gauge an idea of how soon a next release is coming, but most likely if an exploit is found they will release it immediately and may include some of the fixes with it. I don't mind either way as long as we are kept informed about progress.
If the blog changes were major and within 6 days, I'm sure it would be justified. But it's been a month, and the skin diffrence report shows all that only five or six changes need to be made.
QUOTE (steve777 @ Jun 28 2008, 05:23 AM)
Is it just me or does anyone else also think ips are not sticking to what they believe in
I recall they used to say that 'we will not release a product until it has been tested as not good practice to release something and then a few days later have to release updates etc' ... or at least words to that effect ??
I recall they used to say that 'we will not release a product until it has been tested as not good practice to release something and then a few days later have to release updates etc' ... or at least words to that effect ??
The New blog did get tested hard and publically at that... It got once around, twice around, pounded, nailed, re-vamped, bent over, a few punches, a phone call here and there, a cigarette after sex, few cries for help and a doctor to deliver the baby. Where ya been mate?
IMO, I think the Blog update was the best illustration of IPS's commitment and determination to accomodate public outcry by far any product within a short amount of time. I have never seen any thread here build up so quickly compared to the blog when IPS took action. It was amazing and I praise them for it.
Hmm, I'm highly confused lol. I think China J has summed it up pretty well.
Blog 1.4.0 was in public beta testing for over a month. For a very very very long time...just as long as board. When we released Blog 1.4.0 there were absolutely no bug reports open on it, and no known bugs.
We released it back on May 19th.
After release, a few bugs were reported. I'm sorry, but this is how software works...we can't change that.
So on June 25th, again after over a week of public testing and no more bugs reported, we released 1.4.1. That is over a month, certainly not 6 days.
And, for the first time (as my memory recalls) we even included a template difference report like we do with IPB. We don't generally do so with components, but we did this time.
I'm afraid we can't do any better than that unfortunately.
Blog 1.4.0 was in public beta testing for over a month. For a very very very long time...just as long as board. When we released Blog 1.4.0 there were absolutely no bug reports open on it, and no known bugs.
We released it back on May 19th.
After release, a few bugs were reported. I'm sorry, but this is how software works...we can't change that.
So on June 25th, again after over a week of public testing and no more bugs reported, we released 1.4.1. That is over a month, certainly not 6 days.
And, for the first time (as my memory recalls) we even included a template difference report like we do with IPB. We don't generally do so with components, but we did this time.
I'm afraid we can't do any better than that unfortunately.
QUOTE (bfarber @ Jun 30 2008, 06:35 AM)
Hmm, I'm highly confused lol. I think China J has summed it up pretty well.
Blog 1.4.0 was in public beta testing for over a month. For a very very very long time...just as long as board. When we released Blog 1.4.0 there were absolutely no bug reports open on it, and no known bugs.
We released it back on May 19th.
After release, a few bugs were reported. I'm sorry, but this is how software works...we can't change that.
So on June 25th, again after over a week of public testing and no more bugs reported, we released 1.4.1. That is over a month, certainly not 6 days.
And, for the first time (as my memory recalls) we even included a template difference report like we do with IPB. We don't generally do so with components, but we did this time.
I'm afraid we can't do any better than that unfortunately.
Blog 1.4.0 was in public beta testing for over a month. For a very very very long time...just as long as board. When we released Blog 1.4.0 there were absolutely no bug reports open on it, and no known bugs.
We released it back on May 19th.
After release, a few bugs were reported. I'm sorry, but this is how software works...we can't change that.
So on June 25th, again after over a week of public testing and no more bugs reported, we released 1.4.1. That is over a month, certainly not 6 days.
And, for the first time (as my memory recalls) we even included a template difference report like we do with IPB. We don't generally do so with components, but we did this time.
I'm afraid we can't do any better than that unfortunately.
Ageed. Blog is being handled very well currently. There was a long period of stagnation but now we are rolling. My members are very happy with the development. Keep it up guys!
Nobody is twisting your arm and making you install each upgrade. If you don't like upgrading repeatedly, the wise thing to do is wait for a few point releases to upgrade to a new major version. That goes for any software. Any x.0 release should be considered risky.
I hope I'm not taking this off topic......but I noticed in the 1.4.0-1.4.1 upgrade installment there's the blog_css.css......was anything really changed in that file?
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.