From 45d91aed3b286e3ada4b21ec08f7304621380aae Mon Sep 17 00:00:00 2001 From: spwhitton Date: Fri, 12 Jul 2019 06:39:18 +0000 Subject: Added a comment --- .../comment_1_a6897e3cb6089c4f3db3d37e71ff9659._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/apt_releaseinfo/comment_1_a6897e3cb6089c4f3db3d37e71ff9659._comment diff --git a/doc/forum/apt_releaseinfo/comment_1_a6897e3cb6089c4f3db3d37e71ff9659._comment b/doc/forum/apt_releaseinfo/comment_1_a6897e3cb6089c4f3db3d37e71ff9659._comment new file mode 100644 index 00000000..b354208d --- /dev/null +++ b/doc/forum/apt_releaseinfo/comment_1_a6897e3cb6089c4f3db3d37e71ff9659._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="spwhitton" + avatar="http://cdn.libravatar.org/avatar/9c3f08f80e67733fd506c353239569eb" + subject="comment 1" + date="2019-07-12T06:39:18Z" + content=""" +I think that the point of this was to prevent people with 'stable' in their sources.list from accidentally upgrading to a new stable release. Similarly, to prevent users with 'testing' in their sources.list from upgrading to the new testing, when what they wanted to do was track stable+1. + +I think that when a user uses propellor's `Testing` and `Unstable` types they are explicitly requesting a rolling release, so it seems find to pass it for those suites. + +This is not based on reading any discussions about the new feature. Just my own inference as to its purpose. +"""]] -- cgit v1.2.3