Skip to content

Commit 7e4191c

Browse files
authored
Update meilisearch-pre-release-work.md
1 parent 7550ac2 commit 7e4191c

File tree

1 file changed

+17
-10
lines changed

1 file changed

+17
-10
lines changed

resources/meilisearch-pre-release-work.md

Lines changed: 17 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -12,19 +12,15 @@ This issue gathers the changes related to the vX.Y.0 of Meilisearch that will im
1212

1313
📅 Release date: TBD
1414

15-
## TODO
15+
## Timelines & steps
1616

1717
### Pre-release
1818

19-
- [ ] Define (with the help of PMs) which integrations should be updated to include the new features in the latest version of Meilisaearch. Most of the time, it will be tier #1 integrations.
20-
Integration to update: TBD
21-
- [ ] With the help of [this CI](https://github.com/meilisearch/meilisearch/actions/workflows/sdks-tests.yml) running on `rc0`, define in which SDKs we have to update the tests
22-
- [ ] Create a branch by running [Octopus script](https://github.com/meilisearch/integration-automations/tree/main/octopus): only open branches for the integrations we choose to update + Kubernetes repository + Cloud provider repository (changing the version) + SDKs/integrations where we must update the test suite.
23-
- [ ] Update integrations according to the new Meilisearch features (cf below which feature and how 👇)
19+
- [ ] With the help of the Product team and [this CI](https://github.com/meilisearch/meilisearch/actions/workflows/sdks-tests.yml), define which integrations should be updated and how (New feature? Update README? Update tests?) -> **Fill in** the "What to implement?" section below in this issue 👇.
20+
- [ ] Create a branch by running [Octopus script](https://github.com/meilisearch/integration-automations/tree/main/octopus): only open branches for the integrations we choose to update (defined in the previous step) + Kubernetes repository + Cloud provider repository (changing the version)
21+
- [ ] Update integrations according to the decisions (cf "What to implement?" section below in this issue 👇)
2422
⚠️ If possible, this step is done before pre-release, once the feature is ready thanks to the prototype released by the engine team
2523
- [ ] TBD
26-
- [ ] Update integrations having failing test suites with the new RC of Meilisearch (refer to this [CI](https://github.com/meilisearch/meilisearch/actions/workflows/sdks-tests.yml))
27-
- [ ] TBD
2824
- [ ] Add code samples for the chosen up-to-date integrations with the new version of Meilisearch
2925
- [ ] Update the library version of the related integrations and prepare the changelogs
3026

@@ -37,8 +33,19 @@ Integration to update: TBD
3733
- [ ] publish images (steps are in CONTRIBUTING.md)
3834
- [ ] Open issues in the repositories that are not up-to-date with the latest version of Meilisearch (**including code samples**)
3935

40-
## Features to implement
36+
## What to implement?
37+
38+
### Template: feature name
39+
40+
Related issue in the engine:
41+
42+
Brief explanation of the feature and the impact potential impact on the integrations
43+
44+
TODO:
45+
- [ ] JS: TBD
46+
- [ ] PHP: TBD
47+
- [ ] TBD
4148

42-
*TBD: here list the features, link the related specs/issues/PRDs, and some implementation details if necessary*
49+
The following integrations will not have the feature available for the release day: TBD
4350

4451
---

0 commit comments

Comments
 (0)