forked from cwtch.im/docs.cwtch.im
Drafty
This commit is contained in:
parent
9ec21f464c
commit
d09a5db155
|
@ -26,9 +26,9 @@ Back in January we outlined several goals that we would have to fit on our way t
|
|||
(✅ means complete, 🟡 means in-progress, ❌ not started.)
|
||||
|
||||
- By **1st February 2023**, the Cwtch team will have reviewed all existing Cwtch issues in line with this document, and established a timeline for including them in upcoming releases (or specifically commit to not including them in upcoming releases). ✅
|
||||
- By **1st February 2023**, the Cwtch team will have finalized a feature set that defines Cwtch Stable and established a timeline for including these features in upcoming Cwtch Beta releases. ✅
|
||||
- By **1st February 2023**, the Cwtch team will have [finalized a feature set that defines Cwtch Stable](/blog/cwtch-stable-api-design) and established a timeline for including these features in upcoming Cwtch Beta releases. ✅
|
||||
- By **1st February 2023**, the Cwtch team will have expanded the Cwtch Documentation website to include a section for:
|
||||
- [Security and Desin Documents](/security/intro) ✅
|
||||
- [Security and Design Documents](/security/intro) ✅
|
||||
- Infrastructure and [Support](/docs/getting-started/supported_platforms) 🟡
|
||||
- in addition to a new development blog. ✅
|
||||
- By **31st March 2023**, the Cwtch team will have created:
|
||||
|
@ -38,9 +38,9 @@ Back in January we outlined several goals that we would have to fit on our way t
|
|||
- By **31st March 2023** the Cwtch team will have published:
|
||||
- a Cwtch Interface Specification Document ✅
|
||||
- a Cwtch Release Process Document 🟡
|
||||
- Cwtch Support Plan document ✅
|
||||
- a Cwtch Support Plan document ✅
|
||||
- a Cwtch Packaging Document 🟡
|
||||
- and a document describing the [Reproducible Builds Process](/blog/cwtch-bindings-reproducible) ✅
|
||||
- a document describing the [Reproducible Builds Process](/blog/cwtch-bindings-reproducible) ✅
|
||||
- These documents will be available on the newly expanded Cwtch Documentation website 🟡
|
||||
- By **31st March 2023** the Cwtch team will have integrated automated UI tests into the build pipeline for the cwtch-ui repository. ✅
|
||||
- By **31st March 2023** the Cwtch team will have integrated automated fuzzing into the build pipeline for all Cwtch dependencies maintained by the Cwtch team ❌
|
||||
|
@ -63,7 +63,7 @@ Now for the big news, we plan on releasing a candidate Cwtch Stable release duri
|
|||
- By **30th April 2023** the Cwtch team will have also released developer-centric documentation including:
|
||||
- A guide to building Cwtch-apps using official libraries
|
||||
- Automatically generated API documentation for libCwtch
|
||||
- By **31st May 2023** the Cwtch team will have released new Cwtch Beta releases (1.12+) featuring:
|
||||
- By **30th June 2023** the Cwtch team will have released new Cwtch Beta releases (1.12+) featuring:
|
||||
- An implementation of [Conversation Search](https://git.openprivacy.ca/cwtch.im/cwtch-ui/issues/129)
|
||||
- [Profile statuses](https://git.openprivacy.ca/cwtch.im/cwtch-ui/issues/27) and other associated information
|
||||
- An update to the network handling code to allow for [better Protocol Engine management](https://git.openprivacy.ca/cwtch.im/cwtch-ui/issues/593)
|
||||
|
|
Loading…
Reference in New Issue