|[cross-project-issues-dev] Capture Kepler participation information|
Can you please take a look at the Kepler page  to make sure that the entry for your project is correct.
For starters... is your project listed at all? Should it be removed?
Please confirm the version number. If there is no version number, please let me know what version you'll be including in Kepler.
Note that you'll need to have a corresponding release record for the version that you're including in Kepler. You can create a version using the PMI. Any project committer can log into their project page (e.g. ) click on 'Releases' on the left, and then enter information about the release. If you're having trouble with this, please let me know.
Ideally, you can enter information about the release. Minimally, it would handy if you can provide a description. This will help me to disseminate information about your project on your behalf. Note that it is best that you keep this information concise. If you feel a need to provide a lengthy description, consider using the "summary" support to start with a short (e.g. one paragraph) summary with a more lengthy description.
You'll notice that a message indicating that the release is included in Kepler will automagically appear on the release record page (the project page as well).
Note that you do not necessarily need to have a release on the exact date of Kepler. If it makes more sense, then you can provide a release that occurs on any date leading up to the Kepler release date. The bits from whatever release you specify *must* be the bits included in the Kepler repository.
You can also include your plan information directly on the release record and start assembling your review information there as well. There is no specific requirement to do this. You can continue to do what you've been doing all along if you'd prefer.
Note that all projects are required to have a project plan.
I am assembling information regarding the use of the PMI in the wiki . Watch that page for updates.
Back to the top