redstrate/kawari
1
Fork 0
mirror of https://github.com/redstrate/Kawari.git synced 2025-07-23 13:07:45 +00:00
Code Activity

Remove branching policy, add documentation about tags

Browse source 
I think I want branches to be used for new expansions - for example
once Dawntrail is superseded then it will be moved to a branch
called 7.0.

Major/minor patch versions are now treated equally, basically
every time the game version is bumped a new tag is created. I have
created tags for the previously supported patches now. I also
clarified that these are moreso for "historical" purposes and
you shouldn't have any expectations of it building or working. If
you're determined enough, I'm sure you can make it work.
This commit is contained in:
Joshua Goins 2025-07-20 08:40:16 -04:00
parent aa6ec03ffc
commit bfbd4ff8bc
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -36,7 +36,7 @@ Also please don't use Kawari to spoil new or unreleased content, thanks.
## Supported Game Version
Kawari currently supports patch **7.25h3** (2025.06.28.0000.0000.) Kawari will never "roll back" to a previous patch. There are other servers (e.g. Sapphire) that support older versions of the game. As Kawari moves to a new major patch, the previous patch is moved to a branch (e.g. 7.1) These branches are for archival: effectively unsupported, but still useful.
Kawari currently supports patch **7.25h3** (2025.06.28.0000.0000.) Previously supported patches are provided on as tags (e.g. `2025.02.27.0000.0000`.) These may or may not function or build correctly, the tag is moreso a historical marker.
Only the Global region is supported. Only the Windows client is supported. Supporting other regions or clients are currently out of scope of this project, but might work anyway.