← Back to team overview

lubuntu-qa team mailing list archive

Fwd: Xenial Xerus is now open for development

 

Images up now!

---------- Forwarded message ----------
From: Matthias Klose <doko@xxxxxxxxxx>
Date: Tue, Oct 27, 2015 at 9:31 AM
Subject: Xenial Xerus is now open for development
To: ubuntu-devel <ubuntu-devel-announce@xxxxxxxxxxxxxxxx>
Cc: kubuntu-devel@xxxxxxxxxxxxxxxx, lubuntu-devel@xxxxxxxxxxxxxxxx,
xubuntu-devel@xxxxxxxxxxxxxxxx, ubuntu-devel <ubuntu-devel@xxxxxxxxxxxxxxxx>


Xenial Xerus [1] is now open for development, with syncs from unstable
still running.  The development version already starts with some
changes:

 - Python 3.5 already is the default Python3 version.  Aiming for a
   Python2 free desktop for the Xenial release.

 - Binutils is built from the trunk, targeting the 2.26 branch.

 - The launchpad build farm [2] saw some changes.  If you experience
   unexpected build failures without a log, please retry the build.
   If the build failure persists, ask on #ubuntu-devel, or file a bug
   report for the launchpad-buildd project [3].

 - A glibc update will follow later during this cycle.

 - A bunch of library transitions is already triggered by the sync
   from Debian.  Please help finishing such transitions if you see
   them.

 - We expect further updates to some language stacks (ruby, perl,
   golang, node.js, mono, openjdk, and more).

Please don't procrastinate work targeted for Xenial.  We ended the
Wily development cycle with more outstanding build failures and more
outstanding merges than previous release cycles.  An upload doesn't
end when you hit upload, but needs to build, and then migrate to the
release pocket of the archive.  Please follow-up on build failures and
dep-waits [4] and pending migrations to the release pocket [5].

Start working on merges ([6], [7]) now, don't wait until you need a
feature freeze exception for your merge.  You'll see developers much
more xenial than grumpy!

Please check your uploads in a xenial chroot, don't just test in a wily
environment.  See [8] or [9] how to setup such a development chroot.

--
[1] http://www.markshuttleworth.com/archives/1479
[2] https://launchpad.net/builders
[3] https://bugs.launchpad.net/launchpad-buildd/+filebug
[4] http://qa.ubuntuwire.com/ftbfs/
[5]
http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[6] https://merges.ubuntu.com/main.html
[7] https://merges.ubuntu.com/universe.html
[8] https://wiki.ubuntu.com/SimpleSbuild
[9] https://wiki.ubuntu.com/DebootstrapChroot


-- 
Lubuntu-devel mailing list
Lubuntu-devel@xxxxxxxxxxxxxxxx
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/lubuntu-devel



-- 
@wxl | http://polka.bike
Lubuntu Release Manager & Head of QA
Ubuntu PPC Point of Contact
Ubuntu Oregon LoCo Team Leader
Ubuntu Membership Board & LoCo Council Member
Eugene Unix & GNU/Linux User Group Co-Organizer