In Progress

Say hello to Wily Werewolf!

Wiki Upgrade Note

This site is currently under construction. It will deal with Ubuntu development release and some how to's with crash recovery methods and techiques.

Disclaimer

The author of this wiki is not responsible for udpating the wiki data in some of the links that are provided here in devel-testers-wiki. The Mir, SystemD , Unity8 and Wayland wikis and the accuracy of the information therein is the responsiblity of the developers of those projects, however, time permitting, I may append and update outdated information in those areas.

Introduction

Say hello to Wily Werewolf, the next cycle of the most secure operating system on the planet, Ubuntu! Wily will deal with parsing down and cutting away floss and fancy yet still be punchy, snappy and attractive with increased effervescence and even more easy to work with on the desktop and mobile environment.More work on Mir, SystemD, Unity8 and convergence will continue in earnest. Ubuntu, with it's nearly impervious monolithic kernel, will do away with the need for clunky antimalware/virus programs and superfluous firewall systems that munch and hack away at vital resources on all the various different form factors that are available today. Ubuntu does away with nonsense and provides an environment where work can actually be done more efficiently than ever before. But working with Ubuntu is not all an arduous task that requires expert diligence to test and explore. Ubuntu injects a high level of fun and community where all can be involved and testing can actually be a very fulfilling experience. And now , with increased and intense development of Mir and Unity8 the Desktop Experience will be more exciting that ever before.

New Beta Testers Warnings

Wily Werewolf is the codename for the new development cycle. If you are a new Beta tester and want to upgrade your repositories to the new development cycle then you must be advised that there are certain risks of breakage that could take place on your system(s). it is always advised that you have an extra system (hardware) or an extra harddrive to experiment with. If you are not familiar with experimenting with computer hardware or software then U+1 is not the forum for you, however, if you are willing to be on the cutting edge of Ubuntu release and understand that there could be breakage and want to contribute then the Ubuntu community welcomes you and your valued contributions.

New Notes About the Release Schedule

Note about Ubuntu.info file. Make sure to edit Ubuntu.info file after upgrading to next cycle. See here:

Make sure to edit Ubuntu.info file

Special note about Main Server

Make sure you choose Main Server from Other Software after you change your sources list.

New stable method of flashing USBs with .ISOs

Startup Disk Creator has been having problems with reliability. Below is a link where Ubuntu developers/testers found a more stable method to make startup disks on USB flash drives.

New method to make bootable start-up disks.

Download ISO

sudo basically means superusers-do. It is the basic command that gives access to administrative files that may need root authentication. There is a large database on sudo and sudoers definitions and uses in the following links. SudoUbuntuManuals and SudoersUbuntuManual

Here are some common codes of interest to help with Utopic recovery in the event of a crash.

How to find your sources.list - this list is used to set repositories and can be done manually. It is also informative to have on hand if you decide to do a transitional upgrade from Oneiric Ocelot to Precise Pangolin or upcoming Trusty Tahr, now Utopic Unicorn.

gksu gedit /etc/apt/sources.list

Here is a list of commonly used Ubuntu/Linux terminal Codes (not necessarily in order and open to interpretation) of WW Crash Recovery Codes -To be updated:

sudo sed -i 's/vivid/wily/g' /etc/apt/sources.list

sudo apt-get update && sudo apt-get dist-upgrade

sudo apt-get update

sudo apt-get upgrade

aptitude update && aptitude safe-upgrade

sudo update-grub

lspci

lshw

uname -a

lsb_release -a

sudo dpkg -i --configure -a

sudo reboot sudo poweroff

sudo apt-get -f install

sudo apt-get -f remove

sudo apt-get purge nvidia*, sudo apt-get install nvidia-current

sudo service lightdm stop

sudo service gdm start

Instructional Development

Much debate has taken place over using sudo, gksu or pkexec. You will have to decide for yourself which is most secure.

• Pkexec discussion at Ubuntuforums

Mir Testing

If you are interested in installing Mir to test during this cycle then you can use the following links. Note that the Mir wiki has only had minimal updating and so it is not entirely current. It may be better to use the Manually use Sudo Commands link to install Mir and it's components.

• Mir Testers Wiki

  Manualy use Sudo Commands

Here is an UbuntuForum thread where some of us have been doing some preliminary testing.

• Mir performance with glxgears discussion.

Unity8 Testing

• We should use MoinMoin Syntax Parsers (http://moinmo.in/HelpOnParsers) where commands/code are presented. Parsers ensure code/commands are not converted to smileys and other MoinMoin stuff, therefore presented without errors.

• We had some amazing threads, specially since the OO cycle, which maybe we could use here;
• The stickies at Ubuntu+1 have some information that can probably be summarized / simplified here - investigate;
• Add a "What is a development cycle" section: How Ubuntu is developed, by who, where, how, when and where it is released (Alphas, Betas, RCs, etc), who tests it, how it is tested, where bugs are reported, how to report bugs properly, who manages bugs reports, etc. A basic vision of how Ubuntu development works."

• Log files: A lot of people don't know they exist, where they are stored, the type of information available in each log file, how to open them, how to search them easily for valuable information. EDIT:I'll contribute to this portion - I already have something written, as well as log searching scripts posted at Ubuntu+1 threads (posted by Effenberg0x0)

Cleaned!