ubuntu-manual team mailing list archive

[Jason Cook <jason@xxxxxxxxxxx>]

I think that including a meerkat would be cool, but the aren't supposed to
be seen by the end user. *Most* users don't use PPAs or edit the
sources.list file. Even if the did they would be seeing *maverick* and not *
meerkat*.

On Tue, Aug 31, 2010 at 3:39 PM, Yorvyk <yorvik.ubunto@xxxxxxxxxxxxxx>wrote:

> On Tue, 31 Aug 2010 23:47:27 +1200
> Benjamin Humphrey <humphreybc@xxxxxxxxx> wrote:
>
> > Sayantan,
> >
> > We don't want to use references to the code names anywhere in the manual,
> as
> > they're just development names and the user isn't meant to see them.
> >
> > I know Ubuntu versions are often referred to by their development name,
> and
> > unfortunately even end users seem to have picked this up too - but
> Canonical
> > don't mention the development name anywhere when the final release is out
> > and neither should we to be consistent.
> >
> This is not really true.  They are referred to in repositories and PPAs.
> eg. deb http://gb.archive.ubuntu.com/ubuntu/ maverick main restricted
>
>
> > On Tue, Aug 31, 2010 at 10:28 PM, Sayantan Das <sayantan13@xxxxxxxxx>
> wrote:
> >
> > > Can we add a picture of the meerkat on the cover? . It wont be a
> picture
> > > per say, but more like a watermark. It can be done for every new
> release
> > > symbolising the release codename.
> > > Just a thought!
> > >
> > > Regards,
> > >
> > > Sayantan Das
> > >
>
>
> --
> Steve Cook (Yorvyk)
>
> http://lubuntu.net
>
> _______________________________________________
> Mailing list: https://launchpad.net/~ubuntu-manual
> Post to     : ubuntu-manual@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-manual
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Jason Cook