Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of craigmcc@gmail.com designates
 64.233.184.202 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references;
        b=YufwiKC4eTSh5irJUEi4guw6znblfjmcc8Bu9X/VH7ACmzb38eIDpEuVzIdxPKPGAN4bx9tTxYxh4X6NN475Ah1jTEB3PUV4BJgfNVt4cuDysvQhgibP3qcwdYu9Sa4WVkQlaFziZSz5999NHps8UkEe249Wdr0f4j5FxFCeA/w=
Message-ID: <f8b39ace0512011137s39921a1fma8e3239e677e65ef@mail.gmail.com>
Date: Thu, 1 Dec 2005 11:37:59 -0800
From: Craig McClanahan <craigmcc@apache.org>
Sender: craigmcc@gmail.com
To: Struts Developers List <dev@struts.apache.org>
Subject: Re: [PROPOSAL] Target tickets to milestones and use as roadmap
In-Reply-To: <438D4980.70102@twdata.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_47033_9976991.1133465879314"
References: <438D4980.70102@twdata.org>

------=_Part_47033_9976991.1133465879314
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

+1 on Don's proposals to improve tracking and roadmap.

+0 on JIRA ... Bugzilla makes cross-bug references with Commons projects we
depend on a little easier, but that is less important now (most of the
Commons packages we use are pretty stable) than it was earlier.

Craig


On 11/29/05, Don Brown <mrdon@twdata.org> wrote:
>
> I propose we use an automated, easy to understand roadmap that relies on
> Bugzilla tickets marked against Milestones.
>
> With all the action in the Struts project lately, it is hard to see what
> is going on where, and specifically, qualitatively how much work remains
> before a Milestone will be reached.  We need a system that makes it easy
> to see at a glance the roadmap of each Struts subproject, and guide new
> contributions.
>
> I see the solution involving the following:
>   1. All tickets, bugs and enhancements, should be marked against a
> Milestone if accepted
>   2. Any major feature or bug fix committed to svn should have a ticket
> and be assigned to a milestone.
>   3. A ticket should only be marked against a Milestone if a developer
> has committed to work on it
>   4. Once all the all the tickets against a Milestone have been
> resolved, the release is ready to be rolled.
>
> The public face of this solution will be automated roadmap pages, which
> will be generated from Bugzilla reports.  These pages will show, at a
> glance, the status of each subproject, its milestones, and current
> progress toward reaching them.
>
> I've developed a Java console app, driven by a cron, which screen
> scrapes Bugzilla reports to generate a roadmap [1].  As you can see from
> the demo, we don't currently use milestones much at all.  The roadmap is
> an idea taken from Trac [2] and I've personally have had great success
> with this approach of organizing Milestones.
>
> Comments?
>
> Don
>
> [1] http://www.twdata.org/dakine/roadmap/action.html
> [2] http://www.edgewall.com/trac/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

------=_Part_47033_9976991.1133465879314--