Prepare a new release? Version 1.10

[DominusExult]

Hi all,
seems a new version should be prepared. !.8 is plagued by the git fixed weapon ready crash, we have better combat and lots under the hood.
So what are your thoughts? Would you mind going through the bug tracker to find stuff that would make sense to fix before?

Next version should be a 2.0 version :)

@marzojr @drcode1 @wench @tristantarrant @Dragon-Baroque

[wench]

Sounds like a good idea. We could feature freeze the code base right now and it wouldn't make much of a difference as no real active development is occurring right now. Larger work in progress changes would be best deferred till after the 2.0 release. Trying to rush SDL3 or input refactoring into the 2.0 release seems a little risky.

[marzojr]

Sounds like a good idea. We could feature freeze the code base right now and it wouldn't make much of a difference as no real active development is occurring right now. Larger work in progress changes would be best deferred till after the 2.0 release. Trying to rush SDL3 or input refactoring into the 2.0 release seems a little risky.

I agree 1000‰ on all counts.

[marzojr]

Maybe it would be a good idea to temporarily protect master branch? We could require work to be done through pull requests and require reviews until release is done.

[Dragon-Baroque]

Seems a new version should be prepared.

Fully agree. Apart from the "version" name, unless I misunderstand something :

Proposal : Indeed we code freeze master and cut off it a replacement for 1.8 named, say, "1.10". Rather soon.
After that, the snapshots of master take the name "1.90git" or 1.99git" as pre 2.0 and we start discussing 2.0's content and schedule.

Of course, I shall take care of SDL 3, but at the moment, it is not only incomplete and "risky", it is irrelevant until SDL 3.2 comes out as the first public release and gets distributed widely. By now, the next incoming Linuxes of April 2024 only offer SDL 2.30.

[DominusExult]

All fair points and expected :)

Proposal : Indeed we code freeze master and cut off it a replacement for 1.8 named, say, "1.10". Rather soon.

Makes good sense, didn't think of that. I was kind of mind locked into single digits minor versions.

After that, the snapshots of master take the name "1.90git" or 1.99git" as pre 2.0 and we start discussing 2.0's content and schedule.

To prevent us locking ourselves in, I'd propose the next git version to be 1.11 then.

But a port to SDL3, Marzo's SDL event refactoring etc, all warrant a 2.0 release, which should then be the next big goal, IMO. Maybe even, if I dare to dream, the detaching of gumps rendering from map rendering :)

By now, the next incoming Linuxes of April 2024 only offer SDL 2.30.

That's not too far off the last SDL release, to be fair. There have been worse gaps :)

[wench]

detaching of gumps rendering from map rendering

Yeah that would be a 2.0 class feature. With the other big changes I've been waiting for them to be merged before messing with everything

[marzojr]

I would say that next Git version is 1.11, and we change to 1.99 when those major features are ready.

Anyway: add issues here in the project I made for it.

[DominusExult]

Rather than doing my assigned documentation work I'll go through our old bugtracker on SF to see what is still lurking there. So don't be surprised if you get updates from there.