On Thu, May 21, 2015 at 3:48 PM, Christopher wrote:
> @busbey, just a slight clarification to the plan you describe in the
> thread on the user@ list:
>
> Since we'd actually be releasing the latest from 1.5 development
> branch, there won't be any extra dangling unreleased commits to tag
> like
@busbey, just a slight clarification to the plan you describe in the
thread on the user@ list:
Since we'd actually be releasing the latest from 1.5 development
branch, there won't be any extra dangling unreleased commits to tag
like we did for "1.4-development-closed", so there won't be anything
t
+1 for 1.5 EOL
On Tue, May 12, 2015 at 2:18 PM, Christopher wrote:
> How do we want to EOL 1.5?
>
> Personally, I was thinking (soon after 1.7.0 is released):
> * Release and tag 1.5.3
> * Remove 1.5 branch to focus active development on newer versions
> * Be willing to branch from the 1.5.3 tag
> Subject: Re: [DISCUSS] EOL 1.5
>
> So, at this point, I'm willing to do a 1.5.3 release and can start that
> today. It seems we're in agreement we should at least do that.
> Beyond that, I'm not really sure what the consensus is.
>
> --
> Christopher L Tubb
+1 for EOL of 1.5 with the release of 1.5.3
-Original Message-
From: Christopher [mailto:ctubb...@apache.org]
Sent: Thursday, May 21, 2015 1:18 PM
To: Accumulo Dev List
Subject: Re: [DISCUSS] EOL 1.5
So, at this point, I'm willing to do a 1.5.3 release and can start that today
+1 Seems like no one is pushing for a longer lifetime for 1.5. 1.5.3
makes sense.
Eric Newton wrote:
+1 for EOL for 1.5.
Making fixes in 1.5 and then merging it to 1.6, 1.7, and then master is
tedious work. 1.5 makes the task more challenging because the layout of the
packages changed so much
+1 for EOL for 1.5.
Making fixes in 1.5 and then merging it to 1.6, 1.7, and then master is
tedious work. 1.5 makes the task more challenging because the layout of the
packages changed so much in 1.6.
-Eric
On Thu, May 21, 2015 at 1:18 PM, Christopher wrote:
> So, at this point, I'm willing t
So, at this point, I'm willing to do a 1.5.3 release and can start
that today. It seems we're in agreement we should at least do that.
Beyond that, I'm not really sure what the consensus is.
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Tue, May 12, 2015 at 10:35 PM, Josh Elser wrot
1.5 has already started to suffer in terms of landing every bug-fix
there. I don't think it's intentional (I know I have done it though),
but it's kind of a sign that the devs have already mentally move beyond 1.5.
I think JIRA is a clear sign that users aren't heavily using 1.5 (I
can't think
That should read "that could be a good thing" (rather than "that's a
good thing"... I don't know which procedure is better).
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Tue, May 12, 2015 at 6:05 PM, Christopher wrote:
> The rate is already slow, but I understand your point.
>
> An
The rate is already slow, but I understand your point.
And, yes, you are correct, it would likely affect how far back
developers finding bugs in newer versions look to determine the oldest
affected version. In my view, that's a good thing, because it means
less wasted effort if nobody is using tho
that change to development procedure will definitely impact them. it'll
mean folks no longer look for their bugs to impact the 1.5 branch to start
(unless things are critical). that basically guarantees that the rate of
1.5 releases will slow, which impacts ops planning for those on the 1.5
line.
Feel free to include user@ sooner, if you wish. The reason I hadn't
already was because my suggested route would only be a shift in
development procedures, and wouldn't really change things from a user
perspective. Alternatives to what I suggest may affect them more
strongly. We definitely should C
oh! almost forgot. We should get user@accumulo into this conversation
sooner rather than later. I'm not sure if it's better ot just copy them in
to this thread or do it as a follow up once we have more of an idea of what
"EOL" means for them.
On Tue, May 12, 2015 at 1:53 PM, Sean Busbey wrote:
+1 to making sure we have a 1.5.3 before stop dev
I'd like to make sure we get through some testing of 1.5 -> 1.7 upgrade
testing before declaring dev over, just to give people more assurance that
they can upgrade off of the version.
On Tue, May 12, 2015 at 1:18 PM, Christopher wrote:
> How do
How do we want to EOL 1.5?
Personally, I was thinking (soon after 1.7.0 is released):
* Release and tag 1.5.3
* Remove 1.5 branch to focus active development on newer versions
* Be willing to branch from the 1.5.3 tag to rapidly release a 1.5.4
in response to critical bugs
My biggest concerns are
16 matches
Mail list logo
