On 12/06/2017 09:28 AM, Hans Wennborg via cfe-dev wrote:
> Hello everyone,
>
> It's time to start making plans for the 6.0.0 release.
>
> Following our regular schedule, the branch would occur about two weeks
> into January, on Wednesday 17 January 2018, with the goal of shipping
> early March. T
> -Original Message-
> From: Renato Golin [mailto:renato.go...@linaro.org]
> Sent: Thursday, December 07, 2017 11:52 AM
> To: Robinson, Paul
> Cc: Hans Wennborg; Release-testers; llvm-dev; cfe-dev; openmp-dev (openmp-
> d...@lists.llvm.org); LLDB Dev (lldb-dev@lists.llvm.org)
> Subject: R
That works, thanks Jim! Agreed that it is ugly though :-)
-Chris
> On Dec 4, 2017, at 6:18 PM, Jim Ingham wrote:
>
> Yup, apparently debugserver tells us the stop is for exec directly so we
> don't treat it as a breakpoint hit. That sorta makes sense, you don't want
> to trigger a breakpoin
On 6 December 2017 at 21:06, Robinson, Paul via llvm-dev
wrote:
> I'm very sympathetic to syncing upstream stabilization with internal
> processes; that said, branching so soon after New Year's Day (which
> I'd guess is celebrated essentially everywhere) seems like not such a
> great idea. This i
On 6 December 2017 at 17:28, Hans Wennborg via llvm-dev
wrote:
> However, one large consumer of the branch has asked if we could start
> earlier this time, branching on 3 January instead (not moving the ship
> date), to get a longer period for stabilization that syncs with their
> internal process
On 6 Dec 2017, at 18:28, Hans Wennborg via cfe-dev
wrote:
>
> It's time to start making plans for the 6.0.0 release.
>
> Following our regular schedule, the branch would occur about two weeks
> into January, on Wednesday 17 January 2018, with the goal of shipping
> early March. This is the sche
