xubuntu-dev team mailing list archive
-
xubuntu-dev team
-
Mailing list archive
-
Message #02111
[Blueprint client-xubuntu-1305] Xubuntu Issues: The "Saucy" Cycle
Blueprint changed by Stephen Michael Kellat:
Whiteboard changed:
# Remember, we only get 60 minutes alloted for a session.
#
# We may have to break this up potentially to cover multiple time slots.
Issues for discussion:
- 1. The future of GTK in a world where Qt is taking over
- a. Ubuntu is shifting to QML/QT5 to support their shift away from the desktop to covering more platforms
- b. Unit193 raised the point that Lubuntu is considering a [possible shift to Qt](http://irclogs.ubuntu.com/2013/04/26/%23xubuntu-devel.html#t00:15)
- c. Kubuntu is based in Qt
- d. Trend-wise what will this mean for us standing apart in terms of graphics toolkit?
- micahg notes: As long as upstream Xfce is comfortable with GTK, we should be fine, GTK isn't going anywhere, worst possible case is that it drops to universe in which case we can sort out with the Ubuntu GNOME team on how we want to proceed with its maintenance.
- 2. Get more people upload rights (team delegation, sponsored uploads, MOTU...)
+ 1. Get more people upload rights (team delegation, sponsored uploads, MOTU...)
a. The number of people with upload rights is at a dangerously low number
micahg notes: with 2 people, we're ahead of Lubuntu, Ubuntu Studio, and Ubuntu GNOME
b. To improve our resilience, what steps can we take to keep burdens of packaging and uploading from falling on so few shoulders?
micahg notes: we can discuss merges and throwing stuff in the sponsorship queue, the thing to be careful about is getting ahead of the current Xfce in Ubuntu with newer versions; We also try to get most stuff in through Debian and sync
c. Where do we want to go as a community that creates a software product in terms of our own development and growth? Do we want more newly-minted MOTU members by the cycle's end? Do we want more interaction with the Sponsors team by a wider cross-section of our community?
micahg notes: People can get upload rights to just the Xubuntu packageset if that's the limit of interest. While more MOTUs are certainly needed, that's not required to upload to the packageset.
- 3. Which milestone releases will we participate in this cycle?
+ 2. Which milestone releases will we participate in this cycle?
a. For Raring, we participated for both betas
b. Running a single alpha, half way through could help a lot with bug fixes and a group push for testing.
micahg notes: +1 to at least 1 alpha and both betas assuming we can get testers, which alpha(s) will probably depend on if/when Xfce releases 4.12
skellat notes: Xfce 4.12 appears to be rather blocked since 2013-03-15: http://wiki.xfce.org/releng/4.12/roadmap
c. Release dates are posted at https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule and break out this way:
Alpha 1 -- 20 June 2013
Alpha 2 -- 18 July 2013
Alpha 3 -- 1 August 2013
Beta 1 -- 5 September 2013
Final Beta -- 26 September 2013
Notional "Release Candidate" -- 10 October 2013
Release -- 17 October 2013
- 4. What other areas should be included within our offline documentation?
- a. Recap where we went during 13.04
- b. What new horizons need to be mapped during 13.10?
--
Xubuntu Issues: The "Saucy" Cycle
https://blueprints.launchpad.net/xubuntu-desktop/+spec/client-xubuntu-1305