Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
MIME-Version: 1.0
In-Reply-To: <b33a978b-f6b2-6519-62a6-454cee2b1318@apache.org>
References: <CAOzVk0YSaM4OgkhU2WnP3gQ5nCOsYyyc1KtrNB_+oQ6AMGokmw@mail.gmail.com>
 <b33a978b-f6b2-6519-62a6-454cee2b1318@apache.org>
From: Guillaume Ch <gchauvet@gmail.com>
Date: Sat, 11 Feb 2017 18:44:51 +0100
Message-ID: <CAOzVk0ZTiz5enAhAOaJXG3z0oJQ4gffgkKSjJvX9e=nJssDOYA@mail.gmail.com>
Subject: Re: [DAEMON] Feedback on my improvements and new features
To: Commons Developers List <dev@commons.apache.org>
Content-Type: multipart/alternative; boundary=001a114193627c25bb054844c526
archived-at: Sat, 11 Feb 2017 17:44:55 -0000

--001a114193627c25bb054844c526
Content-Type: text/plain; charset=UTF-8

Thank you for your quick response,


> The foundation doesn't have a vision for Daemon. The direction of the
> project is set from the ground up by the community using and developing the
> software rather than from the top down. Project direction is agreed by
> consensus.
> You are proposing a number of potentially significant changes. Some of
> those changes would introduce backwards incompatibilities and require a new
> major release. Others may require a new minor release.


Ok, In my mind all proposal changes targets a 2.0 version to prevent any
backwards incompatibilities with the current 1.0 version.
In summary, I should create ticket per proposals in the Daemon JIRA  and
try to affect them to appropriate version, correct ?

Start a discussion (one at a time) on the proposed new features. Some will
> be accepted as is, some will be accepted with modifications and some the
> community will reject.
>

Did the discussion about a new feature/change will be done on the
mailinglist or on the associated JIRA ticket ?

Regards,

--001a114193627c25bb054844c526--