← Back to team overview

ubuntu-packaging-guide-team team mailing list archive

[Merge] lp:~rpadovani/ubuntu-packaging-guide/1237521 into lp:ubuntu-packaging-guide

 

Riccardo Padovani has proposed merging lp:~rpadovani/ubuntu-packaging-guide/1237521 into lp:ubuntu-packaging-guide.

Requested reviews:
  Ubuntu Packaging Guide Team (ubuntu-packaging-guide-team)
Related bugs:
  Bug #1237521 in Ubuntu Packaging Guide: "Link behind "Ubuntu development release wiki page" points to an obsolete page"
  https://bugs.launchpad.net/ubuntu-packaging-guide/+bug/1237521

For more details, see:
https://code.launchpad.net/~rpadovani/ubuntu-packaging-guide/1237521/+merge/197973

Fixed #1237521
-- 
https://code.launchpad.net/~rpadovani/ubuntu-packaging-guide/1237521/+merge/197973
Your team Ubuntu Packaging Guide Team is requested to review the proposed merge of lp:~rpadovani/ubuntu-packaging-guide/1237521 into lp:ubuntu-packaging-guide.
=== modified file 'ubuntu-packaging-guide/chroots.rst'
--- ubuntu-packaging-guide/chroots.rst	2012-10-19 09:44:44 +0000
+++ ubuntu-packaging-guide/chroots.rst	2013-12-05 23:26:35 +0000
@@ -71,5 +71,5 @@
 
 .. _`Debootstrap Chroot wiki page`: https://wiki.ubuntu.com/DebootstrapChroot
 .. _`EC2 cloud computers`: https://help.ubuntu.com/community/EC2StartersGuide
-.. _`the TestDrive wiki page`: https://wiki.ubuntu.com/UsingDevelopmentReleases
+.. _`the TestDrive wiki page`: https://wiki.ubuntu.com/QATeam/Testdrive 
 .. _`the Security Team Build Environment wiki page`: https://wiki.ubuntu.com/SecurityTeam/BuildEnvironment

=== modified file 'ubuntu-packaging-guide/getting-set-up.rst'
--- ubuntu-packaging-guide/getting-set-up.rst	2013-04-25 18:04:22 +0000
+++ ubuntu-packaging-guide/getting-set-up.rst	2013-12-05 23:26:35 +0000
@@ -24,7 +24,7 @@
   those changes will actually be applied and used. 
 
   Don't worry though, the `Ubuntu development release wiki page 
-  <https://wiki.ubuntu.com/UsingDevelopmentReleases>`_ shows a variety of ways to 
+  <https://wiki.ubuntu.com/QATeam/Testdrive>`_ shows a variety of ways to 
   safely use the development release.
 
 


Follow ups