[llvm][docs] Release process improvements (#175759) Some improvements from working through this getting LLVM 22 off the ground. Most of the changes are pretty straightforward, but one worth mentioning is the change to push the trunk version bump and tag before creating the release branch. This avoids a scenario that was hit for 22 where the release/22.x branch was pushed first and more commits landed in trunk before the 23.0.0git version bump was rebased and committed. The commits landed on trunk during this brief window had the wrong version. This was resolved by cherry-picking the commits to the release branch. It's not entirely clear how big of an issue this really is, but if we can avoid it and make the process less stressful in the process I think it makes sense to do so.
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.