Mailing-List: contact clerezza-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: clerezza-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of tommaso.teofili@gmail.com
 designates 209.85.213.47 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=jLxhM+QPej69u0meEapG51Fx9AfWyrxS8hSjDwvktwBmCzQr4GGxAwcwBBKlKapf52
         0yykdA8BAUEl9S+uHV1QiaxNfQvTOmIPVVCI9lrsacLG+blP97nPF2aupnlvoQ8I0W03
         xOoiFw7EHEWAHDGGBh1kHXKLPLvEHzRT9Rs5s=
MIME-Version: 1.0
In-Reply-To: <BANLkTin1iMsr3kD1dht1uBLaHhRj6ind4Q@mail.gmail.com>
References: <BANLkTikLv59ZBB5=eA4a2zDESC50MAcdfg@mail.gmail.com>
 <02A89B2C-9D7F-4AD8-A9FC-8DA0051EEE4B@bblfish.net>
 <BANLkTin1iMsr3kD1dht1uBLaHhRj6ind4Q@mail.gmail.com>
From: Tommaso Teofili <tommaso.teofili@gmail.com>
Date: Mon, 23 May 2011 10:43:13 +0200
Message-ID: <BANLkTi=+y+B69g9nD8M0oKHQsrEDJce=iw@mail.gmail.com>
Subject: Re: Mailing-List or jira: Where to discuss what
To: clerezza-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=001517592fa0a09a1904a3ed7850

--001517592fa0a09a1904a3ed7850
Content-Type: text/plain; charset=ISO-8859-1

My viewpoint and experience here is that dev mailing list is good for
development discussion regarding architecture and functional topics; in some
cases to discuss high level implementation choices.

So, generally, when developing a new feature (or changing/extending
architecture) I think we should go as follows:

   1. discuss the feature on mailing list: what it brings in, advantages,
   drawbacks, how a user/dev could get added value from it
   2. if it's a "big" feature (in terms of impact on codebase), open an
   "umbrella" jira issue and the related sub tasks for tracking cleanly each
   "isolated" requirement/task (otherwise open a single issue)
   3. discuss per-task implementation details on jira (sub) issues
   4. implement "isolated" changes as much as possible
   5. once each sub task has been resolved then resolve the "umbrella" issue


2011/5/23 Reto Bachmann-Gmuer <reto.bachmann@trialox.org>

> On Mon, May 23, 2011 at 10:00 AM, Henry Story <henry.story@bblfish.net>
> wrote:
> >
> > On 23 May 2011, at 09:31, Reto Bachmann-Gmuer wrote:
> >
> >> The advantage of jira is that the person working on the issues sees
> >> the posted comments, the advantage of the mailing list is to have more
> >> clear threads with more readable subjects.
> >
> > I don't understand your point. I get all the mails from Jira in this
> > mailing list. The advantage of jira is that you can add attachments.
> > And that you can link to other issues.
>

I'd add also that people (users, committers, new developers) can track what
it's been done for a particular feature implementation/bugfix, then, for
example, you can see which changes you made for a particular release using
Jira fields (Fix Versions).
Since one of our goals is also let our community grow I think defining good,
established procedures would not confuse new users/devs and allow them to
understand and contribute easier.
Tommaso


> I think the subject could be more informative and I find it useful
> when subthread can be started and recognized as such. Getting all
> mails with a subject like "[jira] [Updated] (CLEREZZA-...) ..."
> doesn't seem very handy to me. But when I got to jira to pick up an
> issue to resolve or for review I'd like to quickly see what has been
> said on how to resolve the issue and about what has already been said
> about the concrete code committed.
>
> Reto
>
> >
> > Henry
> >
> >
> > Social Web Architect
> > http://bblfish.net/
> >
> >
>

--001517592fa0a09a1904a3ed7850--