New release! Spring 83.0 is out!

[se5a]

meh, much ado about nothing imho.
such people need to get over themselfs.

but anyway, that's unimportant. what is REALY importent is weather these little things get fixed and the official server goes to the new version before the weekend :)
coz... you know.. the weekend...

[jandd]

I hope to update the Debian packages in the next few days. Maybe these will work on Ubuntu too.

I uploaded 83.0 Debian packages to experimental yesterday.

[FLOZi]

In this case a sync-breaking bugfix release, therefore 84 instead of 83.1

Well, a version is just a version. Problem with old versioning system was that we were approaching 1.0. People may have certain expectations for a 1.0 release that we may not be able to meet.

I thought it was
major.sync.release?

The current versioning scheme ensures there is never more than 1 single decimal place.

vMajorRelease.Minorfix

The details of what constitutes a major and a minor release are in the thread in development complete with fancy graphs by Hoijui

Ugh, I must have missed that last step.

Version inflation here we come.

[AF]

It's too late to go on about version numbers, I preferred 27 myself ( this is the 27th major release ), but 83 is out now and we have to be consistent.

[Jools]

Version inflation here we come.

Yeah, there's plenty of that going around these days

Maybe it was Mozilla that started it.

[MidKnight]

All of this is Slackware's fault.

(TBH, though, I prefer 83.0 to 0.83. 2011.1 is the best though.)

[smoth]

you guys are annoyingly obsessed with the fing number scheme.. whatever the devs want to use, as long as they stay to it.

[Karotte]

coz... you know.. the weekend...

[MidKnight]

you guys are annoyingly obsessed with the fing number scheme..

This thread.

[smoth]

you guys are annoyingly obsessed with the fing number scheme..

The people fighting about the decided version numbers...

fixed your link

[FLOZi]

you guys are annoyingly obsessed with the fing number scheme.. whatever the devs want to use, as long as they stay to it.

Precisely why it didn't need changing. The previous system worked with few modifications for what, 6 years now?

In before someone says it was necessary for new git release/dev repo structure.

p.s. I'm in a crabby mood today so I don't mean to be too rude, but on such days molehills sure do loom up out of the ground.

[AF]

The window of opportunity came and went, nobody managed to clamber through. Move on people

[jK]

k seems it needs a bit explaining, so what happened this week:

Sun:

• 83.0 announced
• problems with ZK found (command queue bug, aircraft, ...)
• Licho started work on switch servers

Mon:

• 83.0 should go live this day
• devs were unclear if we shouldn't wait for 84.0
• website was down cause of server switching -> no 83.0 release possible

Tue-Thu:

• website up, wiki down -> still no release possible

Fri:

• finished last things for 84.0
• website up, wiki up, 84.0 `ready`
• buildbot got problems
• hoij, not there
• kloot still commits to develop
• tired
• better don't release in such unknown state

[Licho]

Make 0.84 but not change server. We will test on ZK again?
(You dont need to tag it it can still be 0.83.something)

[varikonniemi]

Ubuntu has updated to 83.0, lobby has not. Am i able to play with some trick, or must i just wait?

[gilboa]

... I'm in the process of pushing 83 into Fedora testing.
Should I continue, or should I wait for 84?

- Gilboa "Just got beaten into a pulp by a single AI player; I really, really suck" Davara.

[wolas]

Suggestion. When there will be next major(will be here? i mean not as fast updates like firefox etc :) ) version out, rename it 8x.0 to 8x.0 beta and post in main spring news something like "8x.0 beta out!!" then wait ~week so not only people who reads forums a lot know about it. So it will be more tested by some curious people and give less problems to packagers :)

[hoijui]

the ultimate solution is, to have proper multi-version support (ZK lobby already has their own version of it, which is, in general, as it will/should be for everything one day). as soon as we have that, we can just release new versions, and nobody would have to suffer if they don't have the latest version yet.
until then, we could possibly announce release testing versions in the news forum/on the front-page (packagers do not have to do anything for them).

[gilboa]

hoijui,

Is 83 considered stable, or should we wait for 84?

- Gilboa

[hoijui]

Sat

• jk and Licho doing some test games with current release branch status
  -> lots of big problems (mostly unseen in 83.0)
• jk fixes some stuff (including a desync)
• hoijui fixes some minor stuff
• late at night: kloot fixes some more stuff (including most/all of the heavy problems found earlier)

if test games today (Sun) work well, we may see 84.0 today.