re[2]: Feedback Needed on Release Reporting Tool

[na...@simulalabs.com]

John

What about updating the "Built with Maven" logo? I will send to you in separate email.  Thanks!


Natalie
----------------------- Original Message -----------------------
 
From: "John Tolentino" <jt...@apache.org>
To: "Maven Developers List" <de...@maven.apache.org>
Date: Sat, 23 Dec 2006 07:13:20 +0800
Subject: Re: Feedback Needed on Release Reporting Tool
 
Here's version 2:

http://people.apache.org/~jtolentino/release-reports/MockReport2.html

You can also find the corresponding xdoc here:

http://people.apache.org/~jtolentino/release-reports/MockReport2.xml

I didn't change the left navigation yet as we're still deciding on
which reports gets linked to and which will be included within the
page.

On 12/23/06, John Tolentino <jt...@apache.org> wrote:
> I see what you mean. I'll post the second version of the mock report
> and let's group it from there. :-)
>
> On 12/23/06, Brett Porter <br...@apache.org> wrote:
> >
> > On 23/12/2006, at 9:13 AM, John Tolentino wrote:
> >
> > >
> > > 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 think these really should be two separate, but related reports. The
> > stable would be:
> >
> > - build status report (for developers, from Continuum, things that
> > need immediate attention like broken build, failing tests, failing
> > ITs, failing checks)
> > - development priorities report (for developers, information on what
> > needs attention at any time)
> > - release readiness report (for developers, information on what needs
> > attention before a release can be cut)
> > - changes/release report (for users, information on what was in the
> > last release. Could also include announcement text, download links,
> > etc).
> >
> > I think the key differences between 2 and 3 are different handling of
> > JIRA. An issue with 1024 votes needs to be scheduled, but it still
> > shouldn't block a release (eg, it's a feature, and the release in
> > question is only a point release). However, a scheduled issue for the
> > point release will block that release and so needs to be considered.
> >
> > WDYT?
> >
> > - Brett
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: re[2]: Feedback Needed on Release Reporting Tool

[Brett Porter <br...@apache.org>]

Hi Natalie,

The logo is somewhat separate - it is part of the overall site  
configuration, not a part of the report. This sample from John is  
just using the current default.

I agree it is a good idea for our little built by logo to default to  
one that matches the main logo on the site, it's just a separate  
discussion.

Cheers,
Brett

On 28/12/2006, at 3:51 AM, <na...@simulalabs.com>  
<na...@simulalabs.com> wrote:

> John
>
> What about updating the "Built with Maven" logo? I will send to you  
> in separate email.  Thanks!
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org