Orxonox

I think we should release more often. The code does not have to be perfect, that's why it is only a 0.1 release, right?

We should gather a list of things we want to have finished before the release. This is the milestone which consists of the tickets we've been working on that last semester. We should close the ones which are finished (only close the ticket if the work is really finished!!). Tickets which we cannot close may generate a new one in the next semester.
I also believe that we don't have all code (the skybox generator?).

I'd like to release the thing before the semester begins, that people which have to think about the PPS have something to download and play.

We would also only be 2 months too late with the release .

What we should achieve. Please make suggestions what we should add or remove from the list.

Must have:

• No segfaulting on any OS.
• Updated wiki (download-page, compile-page)
• binary and code packages for as much infrastructures as possible
• Skybox generator code

Nice to have:

• Well documented code.

I agree, following the creado: release early, release often...
And esp. before the next term.

No segfaulting on any OS.

make that any supported OS - ATM we cannot support OSX, or is someone willing to do it...

I'd like to release the thing before the semester begins, that people which have to think about the PPS have something to download and play.

Full ACK.
And for the next term, I'd like to have a release by the of the term. Thus we should try to keep the presentation branch as hack and workaround free as possible. (If someone need a hack, it is his job to fix it properly.)

Well documented code.

For next term, documented code, or no points. sounds harsh, but at least this way we will get some doku in there.

Skybox generator code

What is so important about this SB generator?

just my .02$
nico

nicolasc wrote:

Skybox generator code

What is so important about this SB generator?

Yeah... we should just drop it. New ticket next semester.

Well, I liked the SG, and the guarantee that everything the students do, will be in the game shouldn't be neglected. If we cannot obtain the code, I agree to do it again, but I think we should at least try and write Gabriel.

We still need those packages of the code and maybe some binaries. Would be REAL cool.
I could do it, but I'm not so familiar where on nautilus I should put it, and a Windows binary is out of scope for me.