1.5.8 release, Dec. 1

["Hyrum K. Wright" <hy...@mail.utexas.edu>]

In light of some of the recent activity on the 1.5.x branch, together
with the policy that we still maintain that branch, I'm planning on
rolling a 1.5.8 release.  Next week will be 1.6.14, the week following
is the Thanksgiving holidays in the States, so I'll push it to Dec. 1,
if nobody has any objections.

I'd invite folks to review 1.5.x/STATUS, and to think about revisions
that we could perhaps merge to 1.5.x, including serious performance,
security or correctness bug fixes.  I don't think we need to fix every
bug in the last 20 months, but if there is something that stands out,
please consider nominating it.

I can't guarantee that this won't be the last release from the 1.5.x
line, but it is definitely a possibility.

-Hyrum

Re: 1.5.8 release, Dec. 1

["C. Michael Pilato" <cm...@collab.net>]

*poke*  (Just a reminder for folks who've not taken a glance at 1.5.x/STATUS
yet.)

On 11/23/2010 10:31 AM, Hyrum K. Wright wrote:
> I know folks are busy (hint, hint) testing and signing 1.6.15, but
> just a reminder that 1.5.8 will roll next week.  In updating CHANGES
> for the release (see r1038163), there is actually some good stuff in
> there already.  Please also review STATUS, so we can get any more
> low-hanging fixes in there.  (I didn't see the 'blame -g' memory fix
> in CHANGES, but it should go into 1.5.8, imho)
> 
> There is also the question of whether a vote for a change on the 1.6.x
> branch constitutes a vote on the 1.5.x, but I'll save that bikeshed
> for another day. :)
> 
> -Hyrum
> 
> On Tue, Nov 9, 2010 at 9:02 PM, Hyrum K. Wright
> <hy...@mail.utexas.edu> wrote:
>> In light of some of the recent activity on the 1.5.x branch, together
>> with the policy that we still maintain that branch, I'm planning on
>> rolling a 1.5.8 release.  Next week will be 1.6.14, the week following
>> is the Thanksgiving holidays in the States, so I'll push it to Dec. 1,
>> if nobody has any objections.
>>
>> I'd invite folks to review 1.5.x/STATUS, and to think about revisions
>> that we could perhaps merge to 1.5.x, including serious performance,
>> security or correctness bug fixes.  I don't think we need to fix every
>> bug in the last 20 months, but if there is something that stands out,
>> please consider nominating it.
>>
>> I can't guarantee that this won't be the last release from the 1.5.x
>> line, but it is definitely a possibility.
>>
>> -Hyrum
>>


-- 
C. Michael Pilato <cm...@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Re: 1.5.8 release, Dec. 1

["Hyrum K. Wright" <hy...@mail.utexas.edu>]

I know folks are busy (hint, hint) testing and signing 1.6.15, but
just a reminder that 1.5.8 will roll next week.  In updating CHANGES
for the release (see r1038163), there is actually some good stuff in
there already.  Please also review STATUS, so we can get any more
low-hanging fixes in there.  (I didn't see the 'blame -g' memory fix
in CHANGES, but it should go into 1.5.8, imho)

There is also the question of whether a vote for a change on the 1.6.x
branch constitutes a vote on the 1.5.x, but I'll save that bikeshed
for another day. :)

-Hyrum

On Tue, Nov 9, 2010 at 9:02 PM, Hyrum K. Wright
<hy...@mail.utexas.edu> wrote:
> In light of some of the recent activity on the 1.5.x branch, together
> with the policy that we still maintain that branch, I'm planning on
> rolling a 1.5.8 release.  Next week will be 1.6.14, the week following
> is the Thanksgiving holidays in the States, so I'll push it to Dec. 1,
> if nobody has any objections.
>
> I'd invite folks to review 1.5.x/STATUS, and to think about revisions
> that we could perhaps merge to 1.5.x, including serious performance,
> security or correctness bug fixes.  I don't think we need to fix every
> bug in the last 20 months, but if there is something that stands out,
> please consider nominating it.
>
> I can't guarantee that this won't be the last release from the 1.5.x
> line, but it is definitely a possibility.
>
> -Hyrum
>