Show Posts
1
General Discussion / Milestone Plan
« on: November 04, 2006, 00:03:28 »
I'm starting to join. I still need to get all my contacts together. I go by ThunderFox on most other forums, most of you should know me by that name.
The first thing I want to bring up is the question of a milestone plan.
What is the current milestone plan? If any? Do you need someone to handle that, and code review?
Obviously the first key component will be to isolate and replace all non-GPL code from source projects, and select libraries. I personally recomend arts for audio. It's never given me trouble on any of the Linux apps I regularly use that utilize it. It also is entirely platform independent.
The second option is to continue with the zDoom system, or to port key functions, such as scripting code, and level function support to another more GPL-friendly Doom engine, such as Doom Legacy.
A third option is the renderer. Should we stick with the current one from zDoom, or put that as a 1.0 requirement as well. I'd once again lean on SDLlib for that. Obviously we need to make up our minds on everything before the first milestone.
The final point is at what point do we make source releases of milestones, and at what point do we make binary releases? Also, how big a bug mandates a backpatches to one of these milestone branches, and what size can be said "just wait for the next milestone"
Regular code cleanups would help, and it seams nobody is assigned to this. You'd be surprised how many bugs can be traced just coincidentally with just this work.
I'd gladly take on these two organization tasks, and be sure to deligate enough that people can work in my absence.
Now I'll head over to the buglist to find a list of bugs that I want to try my luck dirrectly on when I get a SVG logon.
The first thing I want to bring up is the question of a milestone plan.
What is the current milestone plan? If any? Do you need someone to handle that, and code review?
Obviously the first key component will be to isolate and replace all non-GPL code from source projects, and select libraries. I personally recomend arts for audio. It's never given me trouble on any of the Linux apps I regularly use that utilize it. It also is entirely platform independent.
The second option is to continue with the zDoom system, or to port key functions, such as scripting code, and level function support to another more GPL-friendly Doom engine, such as Doom Legacy.
A third option is the renderer. Should we stick with the current one from zDoom, or put that as a 1.0 requirement as well. I'd once again lean on SDLlib for that. Obviously we need to make up our minds on everything before the first milestone.
The final point is at what point do we make source releases of milestones, and at what point do we make binary releases? Also, how big a bug mandates a backpatches to one of these milestone branches, and what size can be said "just wait for the next milestone"
Regular code cleanups would help, and it seams nobody is assigned to this. You'd be surprised how many bugs can be traced just coincidentally with just this work.
I'd gladly take on these two organization tasks, and be sure to deligate enough that people can work in my absence.
Now I'll head over to the buglist to find a list of bugs that I want to try my luck dirrectly on when I get a SVG logon.