Planning for 0.77 Release

[Auswaschbar]

Short facts:
Test builds: http://planetspring.free.fr/spring/
Test lobbyserver: 82.239.138.44:8300


Last release was in January, and its time to make a new one.

So here is the plan:
-> In the next weekend I will make a new 0.77 branch. So you have the next week to add features to trunk which get included in 0.77 (but please don't commit to much experimental stuff).
-> In the next few week we can search and resolve bugs, mod developers can test their mods etc. Bibim's buildserv will make installers of that branch for windows, so everyone can test without much effort.
-> ...
-> Release (maybe August)

Can someone host a lobby server for testing?
What do you think about testing Thursday evening, around 21:00 MEST (19:00 UTC), starting with the 24th Jul?

[LordMatt]

Sounds good to me. I am happy to help test. I think the installer is ready for the new release as it is.

[Satirik]

nice, we could test on the backup server or springlobby's one

[Agon]

If you point me to a svn tarball I could create some rpms for testing.
Maybe the buildbot could create some.

[Noruas]

Please take note that low end graphic cards cannot store the texture properly in the new method you have selected, or chosen, im not really good at explaing things, but when a cheap graphic card whether ati or geforce minimizes, and reloads, it loses the texture on the map, whatever new method is being used, some low end cards cannot support.

[jK]

It's just a typical alttab issue.

Use FixAltTab or move the camera a bit around, so it reloads the textures.

[smoth]

yar, let me know when the test version is ready, I will start doing gundam on it alone.

[clericvash]

I will happily test.

[el_matarife]

-> Release (maybe August)

Realistically there needs to be a bugfix release scheduled for two to three weeks after .77 ships, since I don't think its a great idea to leave a release with known bugs out for 6 months like we just did.

Can someone host a lobby server for testing?
What do you think about testing Thursday evening, around 21:00 MEST (19:00 UTC), starting with the 24th Jul?

It would be a lot easier to get testers if you scheduled a test for the weekend as well.

[Auswaschbar]

-> Release (maybe August)

Realistically there needs to be a bugfix release scheduled for two to three weeks after .77 ships, since I don't think its a great idea to leave a release with known bugs out for 6 months like we just did.

One of the advantages of having a seperate release branch is that bugfix-releases can be made easily without slowing development going on in trunk.

[Agon]

Why not use the Alpha, Beta, RC, Finale(GM) version system.
Like this:
0.77a1, 0.77a2
0.77b1, 0.77b2
0.77rc1, 0.77rc2
0.77

or Kernel like:
0.77.1.1.1
and do more updates for bugfixes.
We are waiting half a year for a bug fix?

The current release system I think is confusing.
That does 0.76b1 means and what 0.76b2?
b = beta?
or an alphabetic/number release system a,b,c for feature changes and 1,2,3 for bug fix releases?

And adding more links to packages and installer like my created rpm packages.
Or the one from packman.

[ZellSF]

Where does latest SVN store its settings? Spring keeps defaulting to 1024x768 fullscreen and it doesn't look pretty.

[rattle]

HKCU\Software\SJ\Spring 0.76b1+

[ZellSF]

Oh. That's uh... weird. thanks.

[el_matarife]

Why not use the Alpha, Beta, RC, Finale(GM) version system.
The current release system I think is confusing.
That does 0.76b1 means and what 0.76b2?
b = beta?
or an alphabetic/number release system a,b,c for feature changes and 1,2,3 for bug fix releases?

I could get behind a new numbering scheme, especially if it made it easier to distinguish between a bugfix and a whole new major version. If it was obvious what releases were a bugfix and what was a new version I bet it would be easier to deal with the various Linux distros that don't like to update packages beyond bugfixes.

[KDR_11k]

Since Spring desyncs if the file versions differ we don't do many bugfix releases.

[Agon]

Since Spring desyncs if the file versions differ we don't do many bugfix releases.

Where is the problem about this?
Who would not update his game if it would run better?
After 1 day most active people have the new version.

Edit:
I'm happy to write this:
Spring SVN packages available for openSuse 10.2 and 10.3 located in my repository: http://download.opensuse.org/repositori ... :/accAgon/
Warning! Java bindings disabled for unitsync due to none free stable java version.

[KDR_11k]

After 1 day most active people have the new version.

Yeah but that's one day of disarray for each release.

[Satirik]

KDR you can force people to update .... that's not really a problem

[clericvash]

I don't see a problem in forcing people to update to play online, we did it before?