I like it, especially all being on one page as Jason said.
Just trying to get to the bottom of the requirements... so this is
something that would always be generated and would measure
"releasability"? ie, you look at the page and see that there are
still 5 issues open for the current version and docck is failing so
it can't be released. I like it.
I agree, I'd basically go for this approach:
- table at the top with all the things in the report that are being
checked, either with a "PASSED" or "FAILED".
- subsections for each thing, linked from the summary. Include actual
failures here for quick investigation, but for success (as well as
failures) show the link to the actual report
For the JIRA side, I'm not sure about showing # votes. I think that's
a separate report that let's you find out what to work on when you
aren't even considering a release. Also, I wouldn't show a list of
closed issues (though link to it) - that's what the changes report
should be for.
I'm thinking this is an aggregation of other reports, so we might
consider how best to construct this, but the prototype is a great
thing to start using now and work towards that.
How does this sound?
- Brett
On 19/12/2006, at 2:19 PM, John Tolentino wrote:
Hi Everyone,
Been working on a tool to generate reports for release candidates and
this is a mock of what it should look like:
http://people.apache.org/~jtolentino/release-reports/MockReport.html
We can send this generated page to the dev list when we call for a
release.
I appreciate any feedback so I can improve the reporting (and before I
go further into implementation).
Thanks,
John
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
