The always awesome [didrocks](https://blog.didrocks.fr) posted yesterday to encourage the testing of the Unity PPA. In this cycle we have changed how Unity is deployed into Ubuntu by required a set of acceptance criteria tests before it enters the archive. As such, much of the testing of the new Unity releases is happening in a PPA and then when a new Unity release is ready, it is added to the 12.04 development branch.
Not only this, but the PPA includes a set of checkbox tests that you can use to provide solid feedback on many different elements of Unity. If you can take a little time to grab the PPA and run through the tests, that would be great.
I have tested this most recent release in the PPA, and I am stunned with how solid Unity feels.
I wanted to share [didrocks’ post](https://blog.didrocks.fr/post/Releasing-a-precise-Unity-5.0-to-Ubuntu-12.04) but his blog is currently down (he knows and is resolving it), so I wanted to republish below. Be sure to grab the PPA and test on 12.04!
Here is the post:
> The [Canonical](https://www.canonical.com) ubuntu platform and product strategy teams are gathering in Budapest this week to tackle as much work as possible on precise pangolin. Despite the promise of snow and cheap beers, we are working hard on getting Unity 5.0 out of the door.
> One of the goal of this release is to increase quality, precision, no regression on the work we push to the unstable version of ubuntu. The desktop experience team made automated and manual tests for that and we can already see the first benefits from it. We pushed an [automated building infrastructure with public test reports](https://jenkins.qa.ubuntu.com/view/Precise%20Unity%20Merger/) to have commits automatically tested, pushed to the [trunk of development branch](https://en.wikipedia.org/wiki/Trunk_(software)) as well as available packages in a ppa.
> With all those news features and requirements, we needed to redesign the release process and that’s what we have done last Monday. Let me expose the few steps I will explain there.
> 1. On Monday evening, we have frozen the trunk, which means, no more new code can enter unity at this point (as well for all the related components like unity-2d, nux, dee, libunity, bamf, unity lenses). Only selected branches can now get in, and those are picked only if they contribute to getting closer to this release quality.
> 2. Then, after ensuring on Tuesday that people can safely install the new release candidate, the [unity-team ppa](https://launchpad.net/~unity-team/+archive/ppa) started to contain the whole latest of what will soon be the 5.0 version of unity. If you install from this ppa, you will see a kind prompt asking you to contribute when logging back to your desktop.
> 3. This prompts help getting to our main goal, which is ensurin the quality of the new release. Multiple things have been put in practice for that. The desktop experience team qualified the release using their manual tests and running automated ones again. [Aurélien](https://agateau.wordpress.com/) and I run our own manual tests (120 of them, trying to covering the whole Unity functionnalities). This finished on Tuesday evening (we rephrased some) and we rebuilt all needed packages again, as well as some other dependencies like update-manager, usb-creator, nautilus, empathy, and gwibber to still make them working when you install from the ppa (ABI bumps). From those test we spotted regressions and get them fixed/fix them, regenerate everything and such.
> 4. The manual test wrapper over checkbox is also automatically installed from the ppa. Which means that *YOU* can help too! I’m bootstrapping this process with the [French Musketeers](https://www.markshuttleworth.com/archives/938) to ensure everything is correct and ready for the next release. How to help there will be widespread for Unity 5.2. More on that soon!
> 5. On Thursday morning, we will collect the results from the tests, see what’s still needed to be fixed (if it’s the case) and then cycle back on the previous steps.
> 6. At the same time, the bugs that are fixed will be milestoned, some cleanup will be done and everything will be then ready to format an explicit text of what’s in the new release.
> 7. Then, the process is well known: we will issue tarballs for every projects we need to upload
> 8. Packaging them properly, with the right build-dependencies and needed tweaks will be done, and upload to precise to share the love!
> 9. Finally, every non fixed bugs but targeted will be reported to the next milestones.
> And that’s it! Everyone will be able to enjoy the whole new shiny Unity 5.0, containing a bunch of bug fixes, as well, as all the layout and ground for being rock solid, speeded up and just… precise Unity version!
