Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of mkienenb@gmail.com designates
 64.233.182.190 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=itbCpEBZWOgmMGaXdoaee9VCa2GEB5NvWDnk5fOc/oSX61AsloN8dw8Gc5/3cJtYx27gtt4pgpS50GC9P1ad9XugHm1P1uFgrkVn8T4xdcYseVs8zrvwn6iq5ajVcSBfkA5+40qd67PRMaIRfYa/1Oh08+L2EGpoUd9BPthbOVc=
Message-ID: <8f985b960604270749p6b9eb9fahc3085a458f15c3a1@mail.gmail.com>
Date: Thu, 27 Apr 2006 10:49:38 -0400
From: "Mike Kienenberger" <mkienenb@gmail.com>
To: "MyFaces Dev mailing list" <dev@myfaces.apache.org>
Subject: Suggestion: Jira issues for all non-sandbox changes
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

One of the things we do for the Cayenne project which has really
helped the Cayenne team out is to create a Jira issue for all changes.
  This makes creating release notes (as well as tracking behavior
changes) easy -- there's always a record of it in issue tracking
system.

I'd like to suggest that MyFaces begins to do the same thing for Impl
and Tomahawk.   I don't consider it to be as important for sandbox
components.

As things stand, someone might fix an unreported bug in snapshot, but
someone else using a released version reports it later, and no one
(other than the fixer) knows that it's already been taken care of.

Worse is the case where someone changes behavior, creating a new
problem "somewhere" in the code, but no one knows who or exactly where
short of searching through every commit message, and the original
person changing the code isn't monitoring the discussion on the issue.