Update unobvious dear-imgui version in README

This commit is contained in:
dbr 2022-11-30 09:57:12 +10:30
parent 59ce49c157
commit b8ddd078c1
2 changed files with 7 additions and 6 deletions

View File

@ -3,7 +3,7 @@
[![Build Status](https://github.com/imgui-rs/imgui-rs/workflows/ci/badge.svg)](https://github.com/imgui-rs/imgui-rs/actions)
[![Latest release on crates.io](https://img.shields.io/crates/v/imgui.svg)](https://crates.io/crates/imgui)
[![Documentation on docs.rs](https://docs.rs/imgui/badge.svg)](https://docs.rs/imgui)
[![Wrapped Dear ImGui Version](https://img.shields.io/badge/Dear%20ImGui%20Version-1.84.2-blue.svg)](https://github.com/ocornut/imgui)
[![Wrapped Dear ImGui Version](https://img.shields.io/badge/Dear%20ImGui%20Version-1.86.0-blue.svg)](https://github.com/ocornut/imgui)
![Hello world](hello_world.png)

View File

@ -18,11 +18,12 @@ Day to day development
When it is time to make a new release, we create a `x.y-stable` branch (e.g `0.9-stable`) from `main`
1. Ensure `CHANGELOG` is up to date
2. Bump `version` in the various `Cargo.toml`
3. A stable branch is created, e.g `git switch -c 0.9-stable` and pushed to Github
4. Create annotated tag `v0.9.0` and push to github
5. Create Release for this version on Github
6. Update and close any relevant tickets
2. Ensure README is up-to-date (including the Dear ImGui Version in badge URL, MSRV)
3. Bump `version` in the various `Cargo.toml`
4. A stable branch is created, e.g `git switch -c 0.9-stable` and pushed to Github
5. Create annotated tag `v0.9.0` and push to github
6. Create Release for this version on Github
7. Update and close any relevant tickets
All further PR's are still done to `main`