commit count might be too much effort? And, yes, I am responsible for that. Sometimes, when getting stuff from the milestones, I pushed them under my name when I was sure the person was already mentioned in the repos anyway. I didn't think that commit count would count!
As to space & maintenance: maybe it's easier to replace the credit image with a text field? Maybe even autoscrolling like many other games do? Then we don't have to drop anyone.
>I didn't think that commit count would count!
Commit count isn't a great metric in any case, it's just one we can very easily get.
>As to space & maintenance: maybe it's easier to replace the credit image with a text field? Maybe even autoscrolling like many other games do? Then we don't have to drop anyone.
I'm going to have a look, but I'm not at all familiar with C4Gui.
Can't we just decrease the font size in the screen by one tick to fit more?
Some issues with that solution:
- C4GUI::TextWindow first does line breaks, then applies formatting. This sometimes breaks the color tags.
- Aligning the titles properly is hard. I may have to hard-code the text width. (They are currently aligned relative to the largest title line in the image file.)
- The original credits image had tons of text shadow to make everything readable. This doesn't seem to be possible with in-game text rendering. I enabled the standard grey background instead, but that doesn't look great.
- C4GUI::TextWindow scrolls the title image together with the text which isn't quite what we want here. Not too bad though as everything seems to fit without scrolling on standard text sizes.
Code: https://github.com/openclonk/openclonk/compare/master...lluchs:c4gui-credits
Edit: windowed mode with 1440x960, I know this is rather exotic and not my usual setting either.
Edit: seems to only happen for wide and low-res resolutions.
But yeah, there are some resolution/font size combination where everything fits, but C4GUI still decides to show scroll bars. I just hope that most players have screens with higher resolutions (at least 1920x1080).
> Also, how do we sort the entries?
I used to order them by how I subjectively thought who contributed the most, taking into account also commits in the resources repos, amount of fixed bugs, blog entries, administrative work etc.
> I must say though, that the commit count alone somewhat leaves out contributions of people who do the artwork (often in the forum) and of the other things I mentioned.
I think commit count works well enough for the dev team. The artwork and music people are in a separate category from those writing code, so there's no unfair competition there. For the "Contributors for 8.0" category, I sorted the artwork contributions somewhere in-between. We only had one very active contributor (Fulgen) anyways, the others all only had a couple commits / pieces of artwork. (I hope I didn't miss anyone contributing artwork, those are a lot harder to detect than commit authors.)
Any release blocking bugs for 8.0?
Any features that we still want to finish before the release?
Do we have any idea why the snapshots are broken?
>Any release blocking bugs for 8.0?
>Any features that we still want to finish before the release?
No, I think everything critical from the bugtracker is fixed.
Apparently it's broken on Mac (there's a Mac issue and Kanibal also mentioned that once), but we don't have any Mac developers to confirm or fix that anyways.
>Do we have any idea why the snapshots are broken?
Yeah, I already wrote ck a message, but he didn't respond yet. It's probably not release-blocking as the releases are built from a separate repository checkout, but we'll need someone with an account (Sven or Maikel I guess?) to try a dry release.
>Do we have a release plan?
- Write a release blog post
- Do the steps from http://wiki.openclonk.org/w/Release_Steps
Anything else?
>Anything else?
Check the roadmap and move everything that's not important to post-8.0.
http://bugs.openclonk.org/roadmap_page.php
And I still have one issue I'd like to fix (#1970)
This is why I'm moving the issues to the "git master" target and not to 9.0. Things that don't block this release won't block the next release either.
> Yeah, I already wrote ck a message, but he didn't respond yet.
He'll have a look this (American) evening. Facebook is the real deal here!
>Anything else?
Oh, and someone could scroll through the changes and write down the ten to twenty (or so) most interesting changes for players and developers, which could be included in a blog posting!
"HEEEY GUYS WE GOT NETWORKZ IMPROVEMENTZ AND IT MIGHT BE THAT YOU CAN NOW JUST JOIN ANOTHER PLAYER IF IT DIDNT WORK BEFORE"
It's advertisement to some degree. You just mention the cool stuff!
Instructions:
The track 'Sea Life' is an updated Version of the main soundtrack, since at that time I used a wrong string patch. Not the strings sound better :)
It should replace the current version.
All other tracks can just be copied into the folder, they are all tagged accordingly and converted to ogg. So nothing needs to be done. Some of the tracks are from a different project than OC and hence a bit darker in their atmosphere though.
[Edit] Also added the additional tracks to the track list in the license.txt, the file is attached to this post.
Clonkonaut, you still have two issues assigned on the roadmap. Do you want to push them to 9.0?
I consider this release blocking, don't know about everyone else. Caesar's assignment isn't fixed. He is currently just working on assignment stuff.
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill