bfarber

Exactly. We will look at feature suggestions when we begin work on 3.1 or whatever.

We will see a beta 5, yes. That is the plan right now at least.

We don't try to keep the features different or similar to any other specific product. We try to keep the features in line with what is requested by the majority of our customers.

However, we are at a beta 4 stage and are not introducing new functionality where possible, so I'm afraid any new features will have to wait until the next version.

While we may test some things in beta releases of browsers, we can never properly support a browser beta release. They have their own bugs which we shouldn't be attempting to correct for.

When FF 3.1 or 3.5 or whatever version they decide to slap on it is released final, we will of course correct any problems within IPB that affect functionality in the new release. Until then, we have to code for Firefox 3.0, as it's the current stable release.

As for why skin bugs aren't worked through as quickly as others - there are several reasons

1) There's one designer and 3 backend developers
2) A lot of the remaining skin bugs are much more challenging to correct than earlier bug reports. Sometimes one bug can take several hours to correct, or requires huge amounts of code to be refactored to correct.
3) Rikki has other work to attend to simultaneously (such as the lofi skin) which may not be listed in the bug tracker, but still needs to be done and takes time.

While we may test some things in beta releases of browsers, we can never properly support a browser beta release. They have their own bugs which we shouldn't be attempting to correct for.

When FF 3.1 or 3.5 or whatever version they decide to slap on it is released final, we will of course correct any problems within IPB that affect functionality in the new release. Until then, we have to code for Firefox 3.0, as it's the current stable release.

As for why skin bugs aren't worked through as quickly as others - there are several reasons

1) There's one designer and 3 backend developers
2) A lot of the remaining skin bugs are much more challenging to correct than earlier bug reports. Sometimes one bug can take several hours to correct, or requires huge amounts of code to be refactored to correct.
3) Rikki has other work to attend to simultaneously (such as the lofi skin) which may not be listed in the bug tracker, but still needs to be done and takes time.

Exactly. killswitch - I see you telling someone else not to skim your posts, but perhaps take some of your own advice and not skim mine. :) I never said release would be in June. In fact, if we released tomorrow (which we're not) it would be before June, and my statement would be perfectly accurate.

We don't know exactly when we will release. Contrary to what some here believe, we also do not base our release dates on our competition. We are setting goals for ourselves to release the software in a stable, working, reliable and secure way for our customers. If that means holding back the release for "6 months" from our original plan to ensure that everything is fully functional, stable and secure - so be it. This is a huge release, a big rewrite from the 2.3 series, and we are aiming to do it right, not "fast".

Exactly. killswitch - I see you telling someone else not to skim your posts, but perhaps take some of your own advice and not skim mine. :) I never said release would be in June. In fact, if we released tomorrow (which we're not) it would be before June, and my statement would be perfectly accurate.

We don't know exactly when we will release. Contrary to what some here believe, we also do not base our release dates on our competition. We are setting goals for ourselves to release the software in a stable, working, reliable and secure way for our customers. If that means holding back the release for "6 months" from our original plan to ensure that everything is fully functional, stable and secure - so be it. This is a huge release, a big rewrite from the 2.3 series, and we are aiming to do it right, not "fast".

Exactly. killswitch - I see you telling someone else not to skim your posts, but perhaps take some of your own advice and not skim mine. :) I never said release would be in June. In fact, if we released tomorrow (which we're not) it would be before June, and my statement would be perfectly accurate.

We don't know exactly when we will release. Contrary to what some here believe, we also do not base our release dates on our competition. We are setting goals for ourselves to release the software in a stable, working, reliable and secure way for our customers. If that means holding back the release for "6 months" from our original plan to ensure that everything is fully functional, stable and secure - so be it. This is a huge release, a big rewrite from the 2.3 series, and we are aiming to do it right, not "fast".

We also can't develop our software solely around the capabilities of developing countries. While we try to cater to as many people as possible, the fact is that most of our customers are from countries where the ability to download IE7 is not an issue.

I still remember downloading Win XP SP1 over dialup - it can be done if someone has the desire. ;)

Uh, you misread my post. I said before June, not in June.

Additionally, we absolutely cannot release the forum upgrade without the components. Customers have purchased these components from us and it is our responsibility to ensure there are compatible versions available for the new version of the forums.

Uh, you misread my post. I said before June, not in June.

Additionally, we absolutely cannot release the forum upgrade without the components. Customers have purchased these components from us and it is our responsibility to ensure there are compatible versions available for the new version of the forums.

Uh, you misread my post. I said before June, not in June.

Additionally, we absolutely cannot release the forum upgrade without the components. Customers have purchased these components from us and it is our responsibility to ensure there are compatible versions available for the new version of the forums.

Uh, you misread my post. I said before June, not in June.

Additionally, we absolutely cannot release the forum upgrade without the components. Customers have purchased these components from us and it is our responsibility to ensure there are compatible versions available for the new version of the forums.

IPB 3.0 will not feature tagging. A future version likely will.

IPB 3.0 will not feature tagging. A future version likely will.

Firstly, I assure you, boards.nbc.com is pretty heavily customized all in all. Trust me - I've done a lot of work on it. ;)



At the end of the day, pushing support for IE6 for another year does JUST that, and we would be having this same discussion then (just like this discussion came up a year ago, and when IE7 first came out - those points we did agree it was too early to move away from IE6).