Hi,
Although I don't run a server myself, I really like this idea. Sticking
to stability saves us a lot of effort.
On 2013? 07? 16? 10:46, William Van Hevelingen wrote:
+1
I think this a great idea. I run all LTS servers and I often just look
at the most recent serverguide for up to date stuff because the LTS
one is usually missing 6+ months of fixes.
William
p.s
Any chance we can switch to Markdown or Restructed text? I've
contributed a few times before and I would really appreciate it if I
didn't have to work with XML.
On Tue, Jul 16, 2013 at 8:33 AM, Peter Matulis
<peter.matu...@canonical.com <mailto:peter.matu...@canonical.com>> wrote:
Hi, I have created a blueprint [1] that affects the Ubuntu Server
Guide
development schedule. After several years of observation both Doug
Smythies and I have decided it makes more sense to publish the
Guide for
LTS releases only. There would be occasional (unofficial)
publications
of the current development branch (snapshots). If this sounds to you
like the rolling release model you are correct, this is what we are
proposing. Other changes include relaxing the string freeze and
translation schedules. I hope to see you there.
peter matulis
[1]:
https://blueprints.launchpad.net/serverguide/+spec/community-1308-serverguide-development
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com <mailto:ubuntu-server@lists.ubuntu.com>
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
--
Thanks,
William
--
John Kim
Ubuntu Doc & Ubuntu QA contributor
IRC: kotux
"Most folks are as happy as they make up their minds to be." -Abraham Lincoln
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
