Re: [PROPOSAL] Create the 1.7.x branch. Like, now.

2011-07-13 Thread Philip Martin
Greg Stein writes: > Heh. Call it "done" and changes come out of the woodwork. (gee, where > have we seen that before?) ... there has been a good dozen changes > today for minor cleanups, packaging, compiler fixes, etc. Nothing > functional, thankfully (for a couple/three weeks, actually). This

Re: [PROPOSAL] Create the 1.7.x branch. Like, now.

2011-07-12 Thread Greg Stein
On Tue, Jul 12, 2011 at 12:50, Greg Stein wrote: > On Tue, Jul 12, 2011 at 10:32, C. Michael Pilato wrote: >... >> What to do about Serf?  I'd like to think that Greg could wrap up his work >> on the single remaining blocking issue in the next week or so.  I've already >> heard (via Hyrum) that h

RE: [PROPOSAL] Create the 1.7.x branch. Like, now.

2011-07-12 Thread Bob Archer
> On Tue, Jul 12, 2011 at 12:22 PM, Hyrum K Wright > wrote: > > > Because I'm a nice guy (and to allow people time to comment), > I'll > > wait until tomorrow morning to create the branch, but plan on it > then. > > +1 Is that a +1 that Hyrum is a nice guy, or that he will wait, or that he shou

Re: [PROPOSAL] Create the 1.7.x branch. Like, now.

2011-07-12 Thread C. Michael Pilato
On 07/12/2011 02:46 PM, Blair Zajac wrote: > > On Jul 12, 2011, at 7:42 AM, Hyrum K Wright wrote: > >> One question that I have is regarding housekeeping. Do we have any >> actions which should be done on trunk (file renames, whitespace >> cleaning, mergeinfo pruning, etc), which will improve ou

Re: [PROPOSAL] Create the 1.7.x branch. Like, now.

2011-07-12 Thread Blair Zajac
On Jul 12, 2011, at 7:42 AM, Hyrum K Wright wrote: > One question that I have is regarding housekeeping. Do we have any > actions which should be done on trunk (file renames, whitespace > cleaning, mergeinfo pruning, etc), which will improve our experience > when merging to the branch? I took m

Re: [PROPOSAL] Create the 1.7.x branch. Like, now.

2011-07-12 Thread Paul Burba
On Tue, Jul 12, 2011 at 12:22 PM, Hyrum K Wright wrote: > On Tue, Jul 12, 2011 at 9:42 AM, Hyrum K Wright wrote: >> On Tue, Jul 12, 2011 at 9:32 AM, C. Michael Pilato >> wrote: >>> The issue tracker currently has *no* non-Serf-related blocker issues open. >>> Per prior agreement, this effective

Re: [PROPOSAL] Create the 1.7.x branch. Like, now.

2011-07-12 Thread Greg Stein
On Tue, Jul 12, 2011 at 10:32, C. Michael Pilato wrote: >... > realize that we'd like to see the tracker sit quiet (blocker-wise) for a > week or so before saying "ship the RC", but I think we need to face some > realities: > >  - blocker-class bugs can -- and will -- crop up after we branch. > >

Re: [PROPOSAL] Create the 1.7.x branch. Like, now.

2011-07-12 Thread Mark Phippard
On Tue, Jul 12, 2011 at 12:22 PM, Hyrum K Wright wrote: > Because I'm a nice guy (and to allow people time to comment), I'll > wait until tomorrow morning to create the branch, but plan on it then. +1 -- Thanks Mark Phippard http://markphip.blogspot.com/

Re: [PROPOSAL] Create the 1.7.x branch. Like, now.

2011-07-12 Thread Hyrum K Wright
On Tue, Jul 12, 2011 at 9:42 AM, Hyrum K Wright wrote: > On Tue, Jul 12, 2011 at 9:32 AM, C. Michael Pilato > wrote: >> The issue tracker currently has *no* non-Serf-related blocker issues open. >> Per prior agreement, this effectively means that there are no known >> blockers, as we have a cont

Re: [PROPOSAL] Create the 1.7.x branch. Like, now.

2011-07-12 Thread Hyrum K Wright
On Tue, Jul 12, 2011 at 9:32 AM, C. Michael Pilato wrote: > The issue tracker currently has *no* non-Serf-related blocker issues open. > Per prior agreement, this effectively means that there are no known > blockers, as we have a contingency plan for Serf already (un-default it).  I > realize that

[PROPOSAL] Create the 1.7.x branch. Like, now.

2011-07-12 Thread C. Michael Pilato
The issue tracker currently has *no* non-Serf-related blocker issues open. Per prior agreement, this effectively means that there are no known blockers, as we have a contingency plan for Serf already (un-default it). I realize that we'd like to see the tracker sit quiet (blocker-wise) for a week o