Jump to content

Second Final 2.2 ?


Guest Please Delete

Recommended Posts

So, I ran version 1.3 for a number of years and was extremely happy with it. In fact it helped my community grow into a really big board.

So finally because of PHP5 coming and wanting to stay current I installed version 2.1.1
Now I know there was a 2.0 final, 2.04, 2.1, 2.1.1 and now 2.1.2

I have read some of the little hick ups with upgrading to 2.1.2 and quite honestly like a lot of people I have many mods installed and upgrading is a big chore.

Looking at the bug list I can see that a 2.1.3 is probably just around the corner.

I've decided to wait until a more final version is available. Maybe when we get to something like 2.2 or Matt can tell us when there is another major release.

I considered 2.1.1 a major release because of the neat new features that is why I did not install 2.0.4 etc.

So hopefully when the later versions come out I will still be able to upgrade even though I missed a couple of upgrades in between. The other thing I would like to see is a manual install of anything that is considered a security issue. So unless that is the case I will hold off for a while because I can live with a few little bugs for now.

Link to comment
Share on other sites

I am with you! I don't understand why IPS wants to keep making all these betas available when they obviously continue to have bug problems. Seems to me that as a company they would want far less headaches and problems for their support department. Why not just let people know what is coming down the pike and wait until a really stable version is available or maybe one somewhat stable beta -- or are the customers just a guinea pig for developing the newer versions to find out what problems they are having? >_<

Link to comment
Share on other sites

Every person does different things with their boards. Some also have their boards on crappy servers and blame IPB and its software for something thats beyond their control. Putting the board into a real world enviroment is the only real way to find problems out. Most quality controlled areas are controlled enviroments. IPB could do something with the board and it runs fine. You do the same thing and you get 100 different errors. It's the nature of the beast.

So you release an update with bug fixes, etc. Well wouldn't you know, know other things have been affected. What used to work fine for one person now doesn't. And what didn't used to work fine for the other person does now. Think of it as a Merry-Go-Round.

All forums run into those common problems.

So you put in a ticket for support on a bug with your forums. They fix it for the next release. Well now when I upgrade, that fix for your board has now done something to mine. The circle continues. There will NEVER, for ANY BOARD ever be a really stable version unless they stop on one version and quit adding things. But even then, bug fixes can lead to more bug fixes.

Link to comment
Share on other sites

In order to create a really good product you need the customers help.
And is it says: BETA is not final, which mean there are still a lot of bugs around which CAN ALSO MEAN that that version is not stable.

And in order to find as many bugs as possible IPB releases BETA vers. to it's customers.
And anyway - it is nearly impossible to find all bugs... although 2.0.4 might have reached that :P

Link to comment
Share on other sites

That is exactly what I am saying, I never install Beta releases, I leave those up to the experts here.

But maybe 2.1 and 2.12 should have been released as Betas.
In which case I would have installed 2.04 as a stable release.

All that said I have really not noticed many bugs on my 2.1 because a lot of them are very specific to certain circumstances.

So like I said I will wait for a more final version instead of installing 2.12 and hopefully they will let us know if a security issue is involved.

Once the bug tracker section get relatively small I will install the next version. This will save me from having to re-do my mods too many times.

Link to comment
Share on other sites

Well thats just it, some of us paid to have mods installed, we modified the skin and language files etc.

For you it may be easy but remember this is not the case for everyone.

Besides, I am not complaining, I am stating that I intent to upgrade only for major releases so as to minimize the amount of times I have to redo the mods and customizations.

They just need to tell us when a release is deemed very important due to security issues. In this particular case I do not think 2.12 was one of them so therefore I will hold off until it becomes necessary to upgrade because of security or a major release.

Simple, no complaints just stating my intention

Link to comment
Share on other sites

I think that's pretty fair, MapleOne. The only keep in mind I have for that is the more updates you apply at one time, the longer it'll take you to adjust mods and skins. Course, that may be less time than to adjust them for each minor release, but I'd need charts and a graph to figure that out ;)

The only reason I bothered with 2.1.2 is that it doesn't affect my skin, and I check the files and they didn't bother my mods. Obviously it's a personal preference issue.

All that said, it's important to remember that IPB isn't trying to release unfinished work. Beta tests can only discover so much. The multitude of differences we end-users have is the often the only real way to determine if there is a bug or not. They probably expected one minor update with 2.1 (after all, it's the nature of the code beast), but not 2.1.2 in such short order. You can't predict how long it'll take to solve a bug. If enough people are clamoring for a fix, do you release a subversion to fix it and annoy people who JUST updated, or do you wait for more and annoy the people who have the problem?

Bleah.

Link to comment
Share on other sites

All that said, it's important to remember that IPB isn't trying to release unfinished work. Beta tests can only discover so much. The multitude of differences we end-users have is the often the only real way to determine if there is a bug or not. They probably expected one minor update with 2.1 (after all, it's the nature of the code beast), but not 2.1.2 in such short order. You can't predict how long it'll take to solve a bug. If enough people are clamoring for a fix, do you release a subversion to fix it and annoy people who JUST updated, or do you wait for more and annoy the people who have the problem?



Bleah.



Thank you. :thumbsup:

From this standpoint, think of it this way (these are not actual numbers, they are hypothetical)...
We have 20 bugs. We have 15 fixes, and 5 remaining to look into (tougher ones, or ones that take longer to fix but aren't critical).

Should we just wait until all 20 are fixed, and leave those affected by the first 15 waiting, so that some members don't have to reinstall all their modifications (which we don't officially support), or do we go ahead and release a build upgrade so the majority of users affected by the first 15 bugs can have their issues addressed more quickly?

Either way, someone isn't going to be happy. But I personally think it's a better idea to release the fixes for the first 15 so the bulk of our users can run a bug-free site, while we work on the last 5 that maybe only a handful of people are affected by.

Many of the existing "bugs" are minor, only affect certain charsets or configurations, or just plain haven't been seen before by anyone. As stated before, it's impossible to know every possible configuration and use of every feature on every server+php setup until the software is out there. We don't want anyone to experience any problems, nor do we want our support department backed up with tickets due to issues here or there. We just want you to get the best quality forum software there is. If you don't wish to reinstall modifications, don't upgrade to 2.1.2. There aren't any security fixes, just bug fixes, and if you can live with those bugs, or they haven't affected you thus far, no one requires you to run the latest version. :)
Link to comment
Share on other sites

Ok a little common sense here. With every single new release, IPS allows people to beta test the software. The big problem is that database conversion scripts are NOT released until the new version comes out of beta and is released. Well when one uses a new database, sure, some problems may be found and reported back. However there are situations that will arise from not testing with live data. This was the case for me. I tested the board with a new database and liked what I saw. Once upgraded the problems manifested.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...