* [devel] насчёт (не)стабильных дистрибутивов и веток
@ 2009-07-26 21:45 Michael Shigorin
0 siblings, 0 replies; only message in thread
From: Michael Shigorin @ 2009-07-26 21:45 UTC (permalink / raw)
To: devel
Здравствуйте.
Понимаю, что тема избитая, но к концу этой старой статьи
есть ряд довольно хорошо сформулированных выводов:
http://lwn.net/Articles/340121/
So, what can be done to make development distributions safer for
a wider community of testers? Absolute safety seems unattainable,
but there are some things which could be done:
* Create a version of the distribution containing packages which
have shown a relatively low level of combustibility. The alpha
releases done by some distributors are a step in this
direction; there is usually an attempt made to stabilize things
a little bit prior to the release. But these releases tend to
leave testers somewhat behind the current state of the art.
Debian's "testing" distribution is probably the best example of
how this can be done on an ongoing basis.
* Provide an indication of the state of the distribution. Many
beaches are equipped with red flags which are posted when
dangerous currents are present. Wouldn't it be nice if an
apt-get upgrade could respond with a message like "the current
threat condition is orange, you may want to reconsider"?
* A built-in rollback system which can undo the effects of an
ill-advised upgrade, even if the system as a whole has been
reduced to rubble. The Btrfs snapshot mechanism should be well
suited to this sort of feature - once Btrfs is stable enough to
be used on a root partition.
--
---- WBR, Michael Shigorin <mike@altlinux.ru>
------ Linux.Kiev http://www.linux.kiev.ua/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2009-07-26 21:45 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-07-26 21:45 [devel] насчёт (не)стабильных дистрибутивов и веток Michael Shigorin
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git