Lines Matching +full:- +full:a

3 *These notes are meant for a maintainer to create official releases.*
5 In preparing a release, create a branch to hold pre-release commits.
11 Some minor bookkeeping updates are needed when releasing a new version of the core library.
21 Use `git log --first-parent v0.7..` to get a sense of the pull requests that have been merged and t…
22 While doing this, gather a couple sentences for key features to highlight on [GitHub releases](http…
25 Use `make doc-latexpdf` to build a PDF users manual and inspect it for missing references or format…
30 1. If making a minor release, check for API and ABI changes that could break [semantic versioning](…
31 …[ABI compliance checker](https://github.com/lvc/abi-compliance-checker) is a useful tool, as is `n…
34 …event release, it's polite to make a PR to support the new release, and it's good for quality to t…
39 The Spack `libceed/package.py` file should be updated immediately after tagging a release.
44 1. `git commit -am'libCEED 0.8.1'`
45 More frequently, this is amending the commit message on an in-progress commit, after rebasing if ap…
47 3. `git switch main && git merge --ff-only HEAD@{1}` fast-forward merge into `main`
48 4. `git tag --sign -m'libCEED 0.8.1'`
50 6. Draft a [new release on GitHub](https://github.com/CEED/libCEED/releases), using a few sentences…
51 7. Submit a PR to Spack.
56 Generate the PDF using `make doc-latexpdf`, click "New version" on the [Zenodo record](https://zeno…
58 Make a new PR to update the version number and DOI in `README.rst` and `doc/bib/references.bib`.
64 * LibCEED.jl, the user-facing package that contains the Julia interface.
65 * libCEED_jll, a binary wrapper package ("jll package") that contains prebuilt binaries of the   li…
67 When there is a new release of libCEED, both of these components need to be updated.
72 The binary wrapper package libCEED_jll is updated by making a pull request against [Yggdrasil](http…
75 diff --git a/L/libCEED/build_tarballs.jl b/L/libCEED/build_tarballs.jl
76 --- a/L/libCEED/build_tarballs.jl
78 @@ -3,11 +3,11 @@
82 -version = v"0.7.0"
87 -    GitSource("https://github.com/CEED/libCEED.git", "06988bf74cc6ac18eacafe7930f080803395ba29")
99 diff --git a/julia/LibCEED.jl/Project.toml b/julia/LibCEED.jl/Project.toml
100 --- a/julia/LibCEED.jl/Project.toml
102 @@ -1,7 +1,7 @@
104  uuid = "2cd74e05-b976-4426-91fa-5f1011f8952b"
105 -version = "0.1.0"
109  CEnum = "fa961155-64e5-5f13-b03f-caf6b980ea82"
110 @@ -26,4 +26,4 @@ Cassette = "0.3"
114 -libCEED_jll = "0.7"
121 $ julia --project=../../.. -e 'include("generator.jl"); generate_ceed_bindings("../../..")'
127 …uld create a PR against the [general Julia registry](https://github.com/JuliaRegistries/General), …
142 …a pull request has the `release preparation` label. One can also use `cibuildwheel --only cp310-ma…
147 1. Create a `~/.pypirc` with entries for `testpypi` (`https://test.pypi.org/legacy/`) and the real …
150 $ twine upload --repository testpypi wheelhouse/libceed-0.8-cp39-cp39-manylinux2010_x86_64.whl
152 3. Test installing on another machine/in a virtualenv:
154 $ pip install --index-url https://test.pypi.org/simple --extra-index-url https://pypi.org/simple li…
156 The `--extra-index-url` argument allows dependencies like `cffi` and `numpy` from being fetched fro…
159 $ twine upload --repository pypi wheelhouse/libceed-0.8-cp39-cp39-manylinux2010_x86_64.whl
166 1. [`libceed-sys`](https://crates.io/crates/libceed-sys), which handles building/finding the `libce…
170 Version numbers are automatically updated using the following, which creates a new commit with the …
173 $ cargo release --no-tag --no-push --no-publish 0.12.0 --execute
178 1. `cargo package --list --package libceed-sys` and `--package libceed` to see that the file list m…
180 3. `cargo release publish --execute` to publish the crates to https://crates.io