PyPRP Release Planning
What needs to be done in the code?
Instructions
If you have any changes to PyPRP that are not in the trunk yet, but you would like to have in the release, please add them to this list, along with a rough estimate of how many weeks it will take you to get it done. Include just the development work in the estimate, not documentation - that will come in a later step. Break independent features down into separate entries as far as possible, and indicate dependencies.
What I imagine to see in this list are finished features from branches that only need to be merged to the trunk, small clean-up work, things that can be brought into beta quality with a small amount of testing, etc. Not big things that haven't even been started yet, that are considered experimental, or that would take a lot of development effort. This is not a wish list, an entry is only made by the person who is willing and able to complete it in the course of a few weeks. I imagine that the list should turn out fairly short, because most things waiting to be released are in the trunk already.
If you are not sure whether your modifications should be integrated into the release or not and would like to discuss this, please indicate so. I personally don't feel qualified to judge the release-worthiness of new features on my own and I hope in such cases a decision can be reached by peer-review from Plasma experts.
Also, if you know about anything that is in the trunk, but should not stay there (because it is unfinished and breaks something, or for whatever reason), please list that here too.
List - add your entries here
-
Feature: Application of modifiers on exportmerged in r387- By: CWalther
- Estimated time: 0 weeks (ready to merge)
- Depends on: nothing
- Needs discussion: no
-
Bugfix: Don't read the whole file into memory when using an hsStream in read modemerged in r388- By: CWalther
- Estimated time: 0 weeks (ready to merge)
- Depends on: nothing
- Needs discussion: no
-
Bugfix: Revision 380 - QuickScript_SoundRegion: multiplayer sync issuemerged in r389- By: D'Lanor
- Estimated time: 0 weeks (ready to merge)
- Depends on: nothing
- Needs discussion: no
-
Feature: Advanced AlcScript properties for DrawableSpansmerged in r392- By: Paradox
- Estimated time: 0 weeks (ready to merge)
- Depends on: nothing
- Needs discussion: no
- Feature: plExcludeRegionModifier
- By: GPNMilano
- Estimated time: 0 weeks (ready to merge)
- Depends on: nothing
- Needs discussion: no
- Feature: plMaintainersMarkerModifier
- By: GPNMilano
- Estimated time: 0 weeks (ready to merge)
- Depends on: nothing
- Needs discussion: no
- Feature: plResponderEnableMsg
- By: GPNMilano
- Estimated time: 0 weeks (ready to merge)
- Depends on: nothing
- Needs discussion: no
- Feature: Advanced AlcScript properties for Sound Classes
- By: GPNMilano
- Estimated time: 0 weeks (ready to merge)
- Depends on: nothing
- Needs discussion: no
- Feature: plEAXListenerMod
- By: GPNMilano
- Estimated time: 2 weeks (but ready to merge)
- Depends on: documentation needed for the individual settings
- Needs discussion: could be implemented to call from a specific list to set the settings rather than setting it all by alcscript. Must also be attached to the soft volume export code as it needs to be attached to a soft volume scene object to work properly
- Feature: PRP_MatClasses
- By: GPNMilano
- Estimated time: 0 weeks (ready to merge)
- Depends on: full documentation needed for all the new settings and changes
- Needs discussion: an age whose materials are not changed will export fine, but the materials will be bright and shiny compared to how they were in previous versions, as well as several mapto changes
-
Bugfix: Revision 385 - Dynamic environment map coordinatesmerged in r390- By: CWalther
- Estimated time: 0 weeks (ready to merge)
- Depends on: nothing
- Needs discussion: no
- Feature: Single-package distribution
- By: CWalther
- Estimated time: 1 week
- Depends on: nothing
- Needs discussion: yes - here