| New Alpha/Beta/0.12 | | What needs done (to be discussed):
Push Trunk->Alpha, Alpha->Beta, Alpha->0.12Make a Driver/Paper directory to publish codes relevant to papers (e.g. FlowRule, Bidisperse); what should be the naming convention? 2012/GranMat14 or 2012/FlowRule? README file?Split MercurySimpleDemos into SelfTests and Demos, add a documentation of all demos. What to do with the selftests that are like demos, e.g. LeesEdwardsSelfTest?Beta/0.12: What about the deprecated warnings?l
| Rules for feature development | | We want a simpler release philosophy: trunk becomes alpha, alpha becomes beta, beta becomes release (instead of merging in changes). Before the next release, we have the following tasks: - Anthony Thornton release 0.11.1, 0.12.beta until June 11
- Anthony Thornton release 0.13.alpha until June 18
- Thomas Weinhart split MercurySimpleDemos into smaller folders
- Thomas Weinhart create Drivers/Paper
- Anthony Thornton update the svn presentation to include new merge commands; can we add part of the svn presentation to the documentation?
- Irana Denissen make all Drivers/ subdirectories compile again (assign subtasks to other developers; Yousef Shaheen should also do some part)
- scordee You mentioned one tutorial is not working as it should; please provide more information (and fix if possible)
|
| Rules for feature development | Developers rules regarding feature development: New features: Develop Trunk should never be in broken state, and should not contain imcomplete features. As a consequence: - Features requiring more than one commit: develop in Branch, then merge into Trunk.
- Small changes requiring only one commit (Bug fixes, etc): Directly directly in Trunk, push to Alpha/Beta as necessary.
|