@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.)
hq.recaptime.dev/wiki/Phorge
phorge
phabricator
Diviner: Correct "Upgrading Phorge" article on release phrequency
Summary: In reality, we do not release weekly, and we do not really cherry-pick from master to the stable branch.
Test Plan: Analyze our activities; run `./bin/diviner generate`.
Reviewers: O1 Blessed Committers, mainframe98
Reviewed By: O1 Blessed Committers, mainframe98
Subscribers: tobiaswiese, valerio.bozzolan, Matthew, Cigaryno
Differential Revision: https://we.phorge.it/D26325
+4
-7
+4
-7
src/docs/user/upgrading.diviner
+4
-7
src/docs/user/upgrading.diviner
···
6
6
Overview
7
7
========
8
8
9
-
Phorge is under active development, and new features are released
10
-
continuously. Staying up to date will keep your install secure.
9
+
Phorge is under active development, and releases are published regularly.
10
+
Staying up to date will keep your install secure.
11
11
12
-
We recommend installs upgrade regularly (every 1-2 weeks). Upgrades usually go
12
+
We recommend installs upgrade regularly. Upgrades usually go
13
13
smoothly and complete in a few minutes. If you put off upgrades for a long
14
14
time, it may take a lot more work to bring things up to date if you want access
15
15
to a useful new feature or an important security change.
···
31
31
branch is a little more stable than `master`, and may be helpful if you
32
32
administrate a larger install.
33
33
34
-
We promote `master` to `stable` frequently, then publish the changelog. During
35
-
the week, major bugfixes are cherry-picked to the `stable` branch. The changelog
36
-
lists the `stable` hashes for that week, as well as any fixes which were
37
-
cherry-picked.
34
+
We promote `master` to `stable` regularly, then publish the changelog.
38
35
39
36
To switch to `stable`, check the branch out in each working copy:
40
37