You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: resources/meilisearch-pre-release-work.md
+17-10Lines changed: 17 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,19 +12,15 @@ This issue gathers the changes related to the vX.Y.0 of Meilisearch that will im
12
12
13
13
📅 Release date: TBD
14
14
15
-
## TODO
15
+
## Timelines & steps
16
16
17
17
### Pre-release
18
18
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 👇)
24
22
⚠️ If possible, this step is done before pre-release, once the feature is ready thanks to the prototype released by the engine team
25
23
-[ ] 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
28
24
-[ ] Add code samples for the chosen up-to-date integrations with the new version of Meilisearch
29
25
-[ ] Update the library version of the related integrations and prepare the changelogs
30
26
@@ -37,8 +33,19 @@ Integration to update: TBD
37
33
-[ ] publish images (steps are in CONTRIBUTING.md)
38
34
-[ ] Open issues in the repositories that are not up-to-date with the latest version of Meilisearch (**including code samples**)
39
35
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
41
48
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
0 commit comments