[cfe-dev] LLVM 3.7 release plans
renato.golin at linaro.org
Tue Jun 23 05:56:44 PDT 2015
On 26 May 2015 at 17:57, Hans Wennborg <hans at chromium.org> wrote:
> - Branch for 3.7 on 14 July 2015
> - Release 3.7 end of August (absolutely no later than 4 September)
Sounds like a plan!
> - Announce the first release candidate on llvm-announce to encourage
> more early testing. Last time many issues were raised late in the
> process. I'm sure that will happen this time too, but announcing the
> RC to a wider audience might help mitigate some of that.
I'm not sure llvm-announce is a larger audience, but won't hurt to CC it.
> - Using CMake for the release binaries. I think I promised we'd do
> this for 3.7. I haven't actually started looking at this yet, but I'm
> still optimistic.
I'm absolutely in agreement with this. Most of us already use CMake
for development, a lot of the buildbots are based on it and I think we
all agree that autoconf is deprecated. Makes no sense to still use it
> - Provide a tarball with the docs and doxygen as part of the release.
There's some of that already, though it never worked too well on my
builds. I never cared, maybe I should.
> - PGP signatures on pre-built binaries: the person who builds the
> binary should sign it (unless you think this is too involved).
I'm ok with this, but we need some process documentation, so that all
of us releasing binaries do the exact same thing or users will be
> - Not including Dragonegg in the release; it seems pretty unmaintaned by now.
I already don't for a long time... Maybe ever. :)
In my wish-list for test-release, in addition to yours, is:
1. Check that all dependencies are met. Libraries, tools, Python
modules, header files, etc. CMake will do most of it, so that may be
covered by the move to it.
2. Check that the things you want to build are actually build. The
script checks out everything (including dragonegg and libc++), but my
final binaries never had any of them. Not even compiler-rt. This one I
*will* start caring *very* soon. I'd like to have both RT and libcxx
3. Actually running the test-suite on the Phase3/install binaries. But
for now, this is not priority for 3.7. I already have a script to do
that on the side, similar to my new CMake test-suite buildbot .
More information about the cfe-dev