Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1257)
Subject: Re: minor Validator improvement
From: Justin Mclean <justin@classsoftware.com>
In-Reply-To: <CB961171.3E202%aharui@adobe.com>
Date: Tue, 27 Mar 2012 10:07:44 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0EDF889A-1C28-4F89-83BF-8F7F24B3A833@classsoftware.com>
References: <CB961171.3E202%aharui@adobe.com>
To: flex-dev@incubator.apache.org

Hi,

> It is for me.  It is supposed to be commit-then-review, not
> =
commit-then-open-jira-issue-then-resolve-jira-issue-then-close-jira-issue-=
th
> en-review. :-)=20

I think putting it in JIRA (in general) is useful as not every one is on =
the dev mailing list and gives wider visibility of changes to users of =
the SDK. It's also easier to search JIRA than the mailing list.

I probably wouldn't of closed the JIRA issue until the change had been =
submitted into to the SDK but each to their own.  I don't think there =
have to be one "true" process that everyone must follow.

Thanks,
Justin=