Skip to content

Commit a07ebe8

Browse files
docs: warn about inappropriate use of bleeding
Use the bleeding package in temporary test environments is fine, but the end user should NOT use it for day by day tasks. Signed-off-by: Claudio André <[email protected]>
1 parent 2980b38 commit a07ebe8

File tree

2 files changed

+12
-0
lines changed

2 files changed

+12
-0
lines changed

docs/newsletter.md

+2
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,8 @@ Besides:
2222
2323
Also:
2424

25+
- end users should NOT use the "bleeding" prerelease for day-to-day tasks;
26+
- instead, they should use the latest released version. See [more here](release-process.md#the-bleeding-release).
2527
- we are trying to attract contributors. We need pull request (PR) reviewers;
2628
- easy task to do:
2729
- if you find something: good;

docs/release-process.md

+10
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,16 @@
1212

1313
- Then, upload the Digitally-signed.tar.gz.asc file to the newly created GitHub release.
1414

15+
## The Bleeding Release
16+
17+
We emphasize that the bleeding version is a trial version. Whenever a new "bleeding" release is created,
18+
all logs and binaries previously called "bleeding" are erased and lost. Therefore, there is an obvious
19+
traceability problem; in addition, it is necessary to highlight the possibility that the bleeding
20+
package is based on commits not suitable for use in production.
21+
22+
Thus, using the bleeding package in temporary test environments is fine, but the end user should
23+
not use it for day by day tasks, which, by the way, is exactly what is happening in the Windows version.
24+
1525
## Tasks for Creating a Release
1626

1727
- [ ] Ensure the `release` branch is up to date and clean;

0 commit comments

Comments
 (0)