Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
In-Reply-To: 
 <CAL5zq9aHK45PqQqH_yaXUuixQ69WsEPGpTswr_bRUiSnZNep1A@mail.gmail.com>
References: 
 <CAGUtCHqDqB12e1z7hSq-KG=1Z7p+DiBZaeokqrYyrBjrZtFVUA@mail.gmail.com>
	<1399317745677.7039b34b@Nodemailer>
	<CAL5zq9aHK45PqQqH_yaXUuixQ69WsEPGpTswr_bRUiSnZNep1A@mail.gmail.com>
Date: Mon, 5 May 2014 15:58:31 -0400
Message-ID: 
 <CALH2pmvzLiiqd6n8AeQwGJkK_G0Kj0xc=tDwc70xysPENEV-dg@mail.gmail.com>
Subject: Re: [VOTE] end of life plan for 1.4 branch
From: Joey Echeverria <joey+ml@clouderagovt.com>
To: dev@accumulo.apache.org
Content-Type: text/plain; charset=UTF-8

On Mon, May 5, 2014 at 3:38 PM, Christopher <ctubbsii@apache.org> wrote:
> I elaborated above, but in short, all previous tags have indicated
> releases. This is standard to publish tags in SCM to denote a release.
> it's confusing to have a tag that does not denote a release. Further,
> having a version that is greater than the greatest approved release
> may mislead people who build from source to use the "latest", thinking
> it was approved and it wasn't.

I agree that 1.4.6-eol is not a good name since it implies a 1.4.6
release that never happened.

I don't agree with the fact that tags are only used in SCM to denote a
release. I think that's the most common usage, but I've always viewed
a tag as any significant point on a branch that signifies not to
expect further changes. The places where those exist in most projects
is for releases and branches that have been EOLed.

-Joey