I don't know what the exact status of NewGVN is, but we generally do
timed releases rather than feature-based releases. If it's ready
before the branch point and doesn't break during the process it goes
in the release, otherwise not.
As far as I know it's not enabled yet, so I'm guessing it might not
end up in the release.
- Hans
On Thu, Jun 15, 2017 at 2:12 PM, Jack Howarth
wrote:
> Out of curiosity, does this mean that enabling the NewGVN pass is
> pushed off until the llvm 6.0 release?
> Jack
>
> On Tue, Jun 13, 2017 at 5:29 PM, Hans Wennborg via Openmp-dev
> wrote:
>> Hello everyone,
>>
>> We're about a month away from the start of the 5.0.0 release process,
>> so it's time for the traditional schedule and call for testers email.
>>
>> If you'd like to help providing binaries and testing for your
>> favourite platform, please let me know and subscribe to the
>> release-testers mailing list [1].
>>
>> This time I will try to delegate a bit more. It's very easy to end up
>> working full time on scanning the commit lists, bisecting bugs, and
>> merging patches --- and I don't have that much time to spend.
>> Especially for bug squashing, I'm hoping to get more of the community
>> involved somehow. Please let me know if you have ideas here.
>>
>> I propose the following schedule for the 5.0.0 release:
>>
>> - 19 July 2017: Create the 5.0 branch, tag RC1 soon after, trunk becomes
>> 6.0.0.
>>
>> - 9 August: Tag RC2; all lose ends should be tied up by now.
>>
>> - 23 August: Final tag. Binaries and release announcement a few days later.
>>
>> Unless there are any concerns, I'll post this on the web page soon.
>>
>> Thanks,
>> Hans
>>
>>
>> [1] http://lists.llvm.org/mailman/listinfo/release-testers
>> ___
>> Openmp-dev mailing list
>> openmp-...@lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
