THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Apply as many patches as possible (6 left to look at) Maven Patches
- Clean up JIRA
- Flush out the duplicates
- Close what issues have been dealt with
- Delete the issues with incomprehensible explanations
- I think if 10 of us when in there for a day we could reduce what cruft there is and discuss how to manage the great information that's in there which we generally don't look at
- Come up with a minimal workflow that at least shows issues that have not been looked at by anyone or categorized. I'm sure we only get 10-20 new issues a day at most so once we initially do a cleanup we should be able to manage this on a daily basis
- Release 2.0.7
- Document making patches so nothing will be accepted without at least working example project, with a preference for unit tests and integration projects
- Make an archetype for test cases
- Make an archetype for ITs
- Document running the ITs
- Modify issue creation screen so that people know what the policy is wrt providing patches
- Dealing with the IT issues I've listed previously (IT Problems)
- Separate the design documents from the Taxonomy (this page)
- Separate out other documents like "How to Help" and our dev processes
- Taxonomy
- The start being the actual home page of the Maven space
- Align JIRA to Taxonomy
- Align Wiki to Taxonomy
...