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: docs/packaging/procedures/release-processes.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,19 +9,19 @@ This post is intended as both information to users, and guidelines for developer
9
9
10
10
## Repository staging
11
11
12
-
All package builds for Solus, updates or otherwise, will always enter the `unstable` repository first. Consequently, all Solus developers and contributors should ensure `solbuild` is configured to use the unstable target. As and when the weekly stabilization efforts have completed, the `unstable` repository will be pulled into `shannon`, the stable target.
12
+
All package builds for Solus, updates or otherwise, will always enter the `unstable` repository first. Consequently, all Solus developers and contributors should ensure `solbuild` is configured to use the unstable target. As and when the weekly stabilization efforts have completed, the `unstable` repository will be pulled into `polaris`, the stable target.
13
13
14
-
This effectively means that `shannon` is a rolling snapshot of `unstable`. Note that the weekly sync will not make each repository match identically - the **tip** of every package in `unstable` will be merged into `shannon`. This ensures that the `shannon` update path is cost-efficient in terms of package availability, and that the delta packages provided on `shannon` match the true update path for those users. Lastly, this also ensures that there are no unintended packages arriving in shannon from older builds.
14
+
This effectively means that `polaris` is a rolling snapshot of `unstable`. Note that the weekly sync will not make each repository match identically - the **tip** of every package in `unstable` will be merged into `polaris`. This ensures that the `polaris` update path is cost-efficient in terms of package availability, and that the delta packages provided on `polaris` match the true update path for those users. Lastly, this also ensures that there are no unintended packages arriving in Polaris from older builds.
15
15
16
-
Solus installations always default to the `shannon` repository, making shannon the published distribution, and `unstable` the development distribution.
16
+
Solus installations always default to the `polaris` repository, making Polaris the published distribution, and `unstable` the development distribution.
17
17
18
18
## Weekly Sync - Every Friday
19
19
20
20
At minimum there shall be one sync per week - this will always be on a Friday. As a result, users are never more than a few days away from unstable. This allows packagers to make deeper changes to Solus and still have time to stabilize the repository before releasing changes on the Friday.
21
21
22
22
Given the high volume of changes within Solus in any sync window, the Friday sync should be viewed more as a release than a simple sync. All developers and contributors should try their best to ensure that their changes do not introduce regressions, and that existing update paths are **always respected**.
23
23
24
-
Minor syncs during the week, and correctional syncs shortly after the Friday-sync, are permitted assuming they do not introduce breaking changes to shannon. These may include minor packaging changes, security updates, etc.
24
+
Minor syncs during the week, and correctional syncs shortly after the Friday-sync, are permitted assuming they do not introduce breaking changes to polaris. These may include minor packaging changes, security updates, etc.
Copy file name to clipboardExpand all lines: docs/user/package-management/repo-management.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,15 +5,15 @@ summary: Repository Management
5
5
6
6
# Repository management
7
7
8
-
Solus offers two main software sources: stable (shannon) and unstable. The `eopkg` package manager can use multiple sources on your system, which is helpful if you use a source provided by another vendor.
8
+
Solus offers two main software sources: Polaris (stable) and Unstable. The `eopkg` package manager can use multiple sources on your system, which is helpful if you use a source provided by another vendor.
| Unstable |`https://cdn.getsol.us/repo/unstable/eopkg-index.xml.xz`| Only use this source if build Solus packages or you test new software before it moves to the stable source. |
0 commit comments