Open the development line at 0.6.0-dev

Reopens master for work after the release. The package version, the status
badge and the roadmap paragraph all move to the in-development form this
branch uses between releases, where they name the version being built rather
than the one last shipped.

The roadmap paragraph returns to the shape it had at 0.5.0-dev: a short
statement of where the branch is, what has shipped, and one sentence
summarising the release just made, rather than the full release description
that belonged to the tag.

The changelog gets an empty Unreleased heading, replacing the note that
pointed at where the release content had been folded.
This commit is contained in:
Johnathan Corgan
2026-08-30 16:01:13 +00:00
parent 80f8f965aa
commit f1245b6675
4 changed files with 14 additions and 29 deletions
-3
View File
@@ -7,9 +7,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased]
Nothing yet. Everything previously staged here is folded into
`[0.5.0]` below.
## [0.5.0] - 2026-08-30
### Added
Generated
+1 -1
View File
@@ -1144,7 +1144,7 @@ checksum = "9844ddc3a6e533d62bba727eb6c28b5d360921d5175e9ff0f1e621a5c590a4d5"
[[package]]
name = "fips"
version = "0.5.0"
version = "0.6.0-dev"
dependencies = [
"arc-swap",
"bech32 0.12.0",
+1 -1
View File
@@ -1,6 +1,6 @@
[package]
name = "fips"
version = "0.5.0"
version = "0.6.0-dev"
edition = "2024"
description = "A distributed, decentralized network routing protocol for mesh nodes connecting over arbitrary transports"
license = "MIT"
+12 -24
View File
@@ -3,7 +3,7 @@
![banner](docs/logos/fips_banner.png)
[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
[![Rust](https://img.shields.io/badge/rust-orange.svg)](https://www.rust-lang.org/)
[![Status](https://img.shields.io/badge/status-v0.5.0-green.svg)](#status--roadmap)
[![Status](https://img.shields.io/badge/status-v0.6.0--dev-green.svg)](#status--roadmap)
A self-organizing encrypted mesh network built on Nostr identities,
capable of operating over arbitrary transports without central
@@ -299,29 +299,17 @@ testing/ Docker-based integration test harnesses + chaos simulation
## Status & roadmap
FIPS is at **v0.5.0** on the `master` branch, the first feature
release since v0.4.0.
[v0.4.2](https://github.com/jmcorgan/fips/releases/tag/v0.4.2) was the
last release on the maintenance line, so how much of this release is
new to you depends on which version you are upgrading from. The core
protocol
works end-to-end over UDP, TCP, Ethernet, Tor, Nym, and Bluetooth on a
global, public test mesh of thousands of nodes.
v0.5.0 is a platform-and-lifecycle release. It adds FreeBSD as a
packaged platform (x86_64 only), OpenWrt setup helpers for an 802.11s
mesh between routers (`fips-mesh-setup`) and for the open `!FIPS` client
SSID (`fips-ap-setup`), and an Android embedding interface for apps that own
their own TUN.
Node health is now determined at start completion and published as
`Degraded` or `Failed`, a node with **no transport up is a fatal
start** rather than a silent one, and shutdown runs a bounded drain
window (`node.drain_timeout_secs`, default 2 seconds) so live traffic
is not cut mid-flight. The `node.discovery.*` configuration table
splits into `node.lookup.*` and `node.rendezvous.*`; a deployed
`node.discovery:` block still loads, folded in with a one-time
deprecation warning. New wire-format work continues to be staged on the
`next` branch for the subsequent release line.
FIPS is at **v0.6.0-dev** on the `master` branch.
[v0.5.0](https://github.com/jmcorgan/fips/releases/tag/v0.5.0) has
shipped; this development line continues the testing-and-polishing
track toward v0.6.0. The core protocol works end-to-end over
UDP, TCP, Ethernet, Tor, Nym, and Bluetooth on a global, public test
mesh of thousands of nodes. v0.5.0 added FreeBSD as a packaged platform,
OpenWrt setup helpers for an 802.11s mesh backhaul and an open client
SSID, an Android embedding interface, a native datagram API addressed by
public key, and published node health with a bounded shutdown drain.
New wire-format work continues to be staged on the `next` branch for the
subsequent release line.
### What works today