Date: Mon, 08 Jan 2018 13:24:16 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 224669] [exp-run] Against projects/clang600-import branch Message-ID: <bug-224669-13-NikRUqL5iA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224669-13@https.bugs.freebsd.org/bugzilla/> References: <bug-224669-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224669 --- Comment #23 from Jan Beich <jbeich@FreeBSD.org> --- When do you plan to merge the branch? Maybe rc1 (circa January 17) is a good time. Not to rush but C++11 bustage is going to haunt us for months, anyway. Pros: - Notifying each maintainer manually is time-consuming but pkg-fallout@ doe= sn't report issues for exp-runs - early QA (e.g., compiler crash reports) is important for /stable/11 and devel/llvm60 stability as upstream rarely has more than 1 patch-level relea= se correcting regressions after a new major release - more frequent testing with clang 6 to figure out ports that block many consumers sooner Cons: - head-amd64 and head-i386 builders are IPv6-only, so downloading all error logs or getting the number of skipped ports maybe inconvenient - clang 6 bustage will be mixed with other -CURRENT bustage - may spoil other base exp-runs (like bug 214864) until more ports are fixed - ports adding workarounds for clang/libc++ bugs and having to track that --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224669-13-NikRUqL5iA>