[arch-general] Roadmap for user-intervention upgrades [was: Still Glibc problems]

Manolo Martínez manolo at austrohungaro.com
Fri Jul 20 19:13:00 EDT 2012

On 07/20/12 at 10:45pm, Tom Gundersen wrote:
> On Fri, Jul 20, 2012 at 9:37 PM, Manolo Martínez
> <manolo at austrohungaro.com> wrote:
> > On 07/20/12 at 09:31pm, Florian Pritz wrote:
> >> On Fri, 20 Jul 2012 15:15:47 -0400 Manolo Martínez <manolo at austrohungaro.com> wrote:
> >> > On 07/20/12 at 02:56pm, Daniel Wallace wrote:
> >> > > All of those changes were discussed by the devs on arch-dev-public
> >> >
> >> > I, for one, thought that running archlinux responsibly only committed me
> >> > to subscribing to and reading arch-announce and -general. If I need to
> >> > read -dev-public too I will, but it'd be good to be explicit about this.
> >>
> >> You don't have to read arch-dev-public if you just want to use Arch, but
> >> your original question was about the reasoning behind the move and that
> >> information is available in the mailing list archives.
> >
> > No, apparently you do need to know why and how these things are done even if you just
> > want to use Arch and don't plan to develop for it. That's a lesson I learnt around here anyway.
> The aim is that reading the news items should be enough to deal with
> any update. If you want notifications in advance of future plans or if
> you want to understand the reasoning behind certain changes, then
> following arch-dev-public should be enough. arch-general is typically
> for user discussions, and not so much for development discussions.

OK. I'll subscribe to arch-dev-public, then. I think it would be good if
the "mailing lists" page at archlinux.org explained what one is to
expect from each mailing list, and maybe recommend which mailing lists
to follow, like you just did.


More information about the arch-general mailing list