RFC: Dropping support for old wxWidgets releases (2.8 in particular)

[MortenMacFly]

We talked about that for quite some time now. For me, I understood we do that step by step:
1. Provide wx28 and wx30 nightlies for testing
2. Provide only wx30 nightly builds to enforce testing once we don't get serious errors
3. Switch with release

We did step 1. We can do step 2 now, if you like.

[oBFusCATed]

Morten: We're already at step 2? Or by step 2 you mean remove project files for wx2.8?

[MortenMacFly]

Morten: We're already at step 2? Or by step 2 you mean remove project files for wx2.8?

We provide wx31 but not wx30. If you intend to switch to wx30 then this should be tested. Maybe I don't get the point?

[oBFusCATed]

The plan is:
- use wx30 for linux,
- use wx31 for windows and macos.
- delete wx28 projects for linux/macos
- delete wx30 projects for windows.

We cannot use wx30 on windows, because it doesn't have enough hidpi features, as far as I know.

[MortenMacFly]

The plan is:
- use wx30 for linux,
- use wx31 for windows and macos.
- delete wx28 projects for linux/macos
- delete wx30 projects for windows.

We cannot use wx30 on windows, because it doesn't have enough hidpi features, as far as I know.

OK, go ahead!

[BlueHazzard]

We cannot use wx30 on windows, because it doesn't have enough hidpi features, as far as I know.

but hasn't wx3.1.2 a fatal crash bug if you use code completion pop up?
found the report by Miguel Gimenez and i am hitting this too
http://forums.next.codeblocks.org/index.php/topic,23291.msg158701.html#msg158701

[Edit: specify wxWidgets version]

[oBFusCATed]

Yes, 3.1.2 is broken for cb. We need 3.1.3 or wx-master ;( This is why night builds are still on 3.1.1.

[killerbot]

no idea when wx 3.1.3 might arrive, but maybe we could switch for the nightlies to wx master till 3.1.3 arrives ?

[oBFusCATed]

Yes, but which master? It is really bad situation.

[killerbot]

oh, I assumed their would be 1 master ?

[oBFusCATed]

There is only one master, but which point/commit should we choose?

[Miguel Gimenez]

The wx3.1.3 release is estimated for september, so there is no real need to use wx-master now.

The only advantage would be prerelease bug detection in wx (like the wxPopup issue that invalidated 3.1.2)

[oBFusCATed]

There are several fixes for toolbars in wx-master, which are useful to us.
Also relying on wx's schedule isn't a good idea.

[killerbot]

The wx3.1.3 release is estimated for september, so there is no real need to use wx-master now.

The only advantage would be prerelease bug detection in wx (like the wxPopup issue that invalidated 3.1.2)

ok let's wait on this one, and if that one still have to many bugs, then we can think of wx-master ...

[sodev]

There is only one master, but which point/commit should we choose?

My usual approach is to check the log messages to not pick a commit that is in the middle of a series, but usually they don't merge these commits individually but only as whole branch from a PR. Then i try to estimate how dangerous the recent commits are and depending on that i wait a little to see if follow ups get commited. And then i usually take what git fetch gives .