Skip to content

Commit a0feb92

Browse files
committed
[nop] Update README
1 parent c9a959b commit a0feb92

File tree

1 file changed

+6
-25
lines changed

1 file changed

+6
-25
lines changed

README.md

Lines changed: 6 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,8 @@
11
<a href="https://www.taoensso.com/clojure" title="More stuff by @ptaoussanis at www.taoensso.com"><img src="https://www.taoensso.com/open-source.png" alt="Taoensso open source" width="340"/></a>
2-
[**API**][cljdoc] | [**Wiki**][GitHub wiki] | [Latest releases](#latest-releases) | [Slack channel][]
2+
[**API**][cljdoc] | [**Wiki**][GitHub wiki] | [Slack][] | Latest release: [v1.0.0-RC1](../../releases/tag/v1.0.0-RC1) (2024-02-26)
3+
4+
[![Clj tests][Clj tests SVG]][Clj tests URL]
5+
[![Graal tests][Graal tests SVG]][Graal tests URL]
36

47
# Tempel
58

@@ -13,15 +16,6 @@ Its [tiny API](../../wiki/1-Getting-started#api-overview) and focus on **smart k
1316

1417
⚠️ Tempel is [NOT intended](../../wiki/3-Faq#can-i-decrypt-tempel-data-with-other-tools) for interop with other cryptographic tools/APIs!
1518

16-
## Latest release/s
17-
18-
- `2024-02-26` `v1.0.0-RC1`: [release info](../../releases/tag/v1.0.0-RC1)
19-
20-
[![Clj tests][Clj tests SVG]][Clj tests URL]
21-
[![Graal tests][Graal tests SVG]][Graal tests URL]
22-
23-
See [here][GitHub releases] for earlier releases.
24-
2519
## Why Tempel?
2620

2721
- **Easy-to-use, high-level API** focused on [common tasks](../../wiki/2-Examples) like logins, encryption, signing, etc.
@@ -85,20 +79,7 @@ See for intro and usage:
8579

8680
- [Wiki][GitHub wiki] (getting started, usage, etc.)
8781
- API reference via [cljdoc][cljdoc]
88-
- Support via [Slack channel][] or [GitHub issues][]
89-
90-
## Roadmap
91-
92-
Tempel has a **fixed scope**, and is **fully complete**. I'm happy with its design and implementation, and believe it meets all its objectives in its current form. I'm not anticipating significant changes.
93-
94-
Still, given the sensitivity of the problem domain, I plan to approach Tempel's official stable release as a phased rollout to allow time for feedback before locking things down:
95-
96-
| Phase | Date | Release | Appropriate for |
97-
| :---: | :------ | :----------- | :---------------------------------------- |
98-
| 👉 | 2024-02 | `v1.0-RC1` | Staging, with ephemeral or low-value data |
99-
| | 2025-05 | `v1.0` final | Production, with real data |
100-
101-
`v1.0` final will be considered "**done**"- the library is expected to need+see only minimal maintance from that point.
82+
- Support via [Slack][] or [GitHub issues][]
10283

10384
## Disclaimer
10485

@@ -126,7 +107,7 @@ Licensed under [EPL 1.0](LICENSE.txt) (same as Clojure).
126107
[GitHub releases]: ../../releases
127108
[GitHub issues]: ../../issues
128109
[GitHub wiki]: ../../wiki
129-
[Slack channel]: https://www.taoensso.com/tempel/slack
110+
[Slack]: https://www.taoensso.com/tempel/slack
130111

131112
[Peter Taoussanis]: https://www.taoensso.com
132113
[sponsor]: https://www.taoensso.com/sponsor

0 commit comments

Comments
 (0)