On 12/23/06, Brett Porter <[EMAIL PROTECTED]> wrote:
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.
That's the idea, so we'd have more regular releases. For now, the
person calling for the release would have to generate the site and
stage it somewhere for people to see.
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
I get what you mean.
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.
The vote is an indicator that we're prioritizing what the community
needs/wants to get fixed. I think this would be of interest for those
making a vote for the release, if the issues they want fixed will go
in.
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?
Working on version 2 of the mock reports now. Will post it again when
I'm done consolidating the feedbacks but I'm almost done.
- 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
