IPB 2.3 Bug Reports

[Guest]

Just curious, with the original IP.Board section closed in the tracker, where would bug reports for 2.3.6 go? Or do we just not worry about them at all anymore, and wait for 3.0?

[Michael]

I would assume you should check to see if the bug in question still exists in 3.0.0 (if it is possible to check that bug at this point in the beta process), and if so, report it there.

[Mert]

Well, only the button is removed. You can report a new bug from right there: http://forums.invisionpower.com/index.php?...&newissue=2 :)

That link is probably a bug of the Bug Tracker (ironic?) but who cares? :P

[Mark]

There will be no more releases to the 2.3 line assuming nothing major comes up (like the 2.3.5 spam problem) so don't worry about them unless they're also present in 3.0.

[Guest]

Well, only the button is removed. You can report a new bug from right there:

http://forums.invisionpower.com/index.php?...&newissue=2

:)

That link is probably a bug of the Bug Tracker (ironic?) but who cares? :P

:lol:

There will be no more releases to the 2.3 line assuming nothing major comes up (like the 2.3.5 spam problem) so don't worry about them unless they're also present in 3.0.

Alright. Turns out it was an issue with my skin, anyway. Thanks though! :)

[Lewis P]

Well, only the button is removed. You can report a new bug from right there:

http://forums.invisionpower.com/index.php?...&newissue=2

:)

That link is probably a bug of the Bug Tracker (ironic?) but who cares? :P

Please report: http://forums.invisionpower.com/index.php?...;showproject=21

:lol:

[Alex]

I wouldn't vouch to say thats a bug with IP.Tracker. IPS use 1.1.1, I use 1.3.0 Preview, theres a big gap in releases there :P Anyway, won't be long until IPS are at 1.3

[bfarber]

Bugs with tracker, if still present in current versions, should be reported to the tracker category ;)

We have no intentions to release bug fix releases of 2.3 at this point. Naturally we will still address security issues. If the bug exists in 3.0 report it to that category, otherwise we'd simply be marking the bug fixed anyways.