Mailing-List: contact dev-help@fineract.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@fineract.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <014601d14213$027b1e50$07715af0$@confluxtechnologies.com>
References: <DUB127-W25216222B0DEF9F79B4ACD95E70@phx.gbl>
	<DUB127-W95A6146D5DC9194E52CF3595E70@phx.gbl>
	<CABD8fLXCmx+EdfqytE0bHjAN4ESHwg=wE-hpuSkL-Cz7Odo=vw@mail.gmail.com>
	<CA+ULb+uua-8vL85kj+N0RsQnEjYt5Q4sYhNUkXuEtSQfhuCWpg@mail.gmail.com>
	<DUB407-EAS3101C49BBD48B3ACCED831395E70@phx.gbl>
	<CABD8fLXjJMzwQEehpH-avBJS6MqOAooUufFrLSdoKnF6EDUK5Q@mail.gmail.com>
	<DUB127-W1F5B7C308A54FBCF9470295F80@phx.gbl>
	<014601d14213$027b1e50$07715af0$@confluxtechnologies.com>
Date: Tue, 29 Dec 2015 09:04:31 -0600
Message-ID: 
 <CABD8fLXCitQSOMskcFuH9VR=EfycFJd2+R97p6XzT6_ZCoCXZg@mail.gmail.com>
Subject: Re: [DISCUSS] Git procedure and branching model
From: Greg Stein <gstein@gmail.com>
To: dev@fineract.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a114269521c6c5305280abdc3

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

On Tue, Dec 29, 2015 at 2:29 AM, Adi Raju <adi.raju@confluxtechnologies.com>
wrote:
>...

> Do we allow releases to be made with known bugs?
>

In my 30 years of professional software experience ... YES.

There are always bugs in the software that gets released. Some known, some
unknown. If there are *known* bugs, then the community can decide to:
release, release with documentation, or hold to fix. ... but (again) in my
experience many people prefer a new release (albeit with problems) rather
than nothing. Scope the bug, document it, let people know if it may affect
them, then release the code.

You simply cannot hold software until all known bugs are resolved. You'll
never release. It's a balancing act, and a documentation issue.

Cheers,
-g

--001a114269521c6c5305280abdc3--