Re: Inquiry: NGINX branch to track in "Interim" Non-LTS Releases

2018-08-07 Thread Christian Ehrhardt
On Tue, Aug 7, 2018 at 7:14 PM Thomas Ward  wrote:

> Currently, all LTS versions of Ubuntu that are currently supported have a
> version of the NGINX Stable branch in the repositories.  This was done
> initially so that we can provide a 'stable' and 'released without new
> features' type of branch we would be able to track.  In the cycle before
> release, we kept it in line with NGINX Mainline because once NGINX Stable
> was cut from that Mainline branch, they'd have newer features that would
> otherwise have been unavailable if we had tracked Stable.
>
> My assumption is we want to still do this type of behavior (that is, track
> Mainline branch) in interim releases.  This lets the interim releases of
> Ubuntu work with newer features that NGINX introduces, allowing us to file
> bugs upstream as necessary with the Mainline builds or to debug issues as
> they arise in the packaging.  However, because I am not sure if this is
> what we wish to do, I thought I'd reach out to the rest of the Server Team
> for your input.
>
> What do you think would be best, tracking NGINX Stable, or tracking NGINX
> Mainline, for the interim non-LTS releases?  I'm leaning towards tracking
> Mainline in the interim releases, if there's no objection - it'll let users
> who want more cutting edge NGINX features to use those in the interim
> releases without having to force them to use the PPAs.
>
Hi Thomas,
yeah I'd prefer to track Mainline in non-LTS releases as well.

To the sole exception of being very careful toward the next LTS to not
being forced to decide to "go back" or "stay on mainline" for the next
Ubuntu LTS.
For example if NGINX 1.17 mainline would be in Ubuntu 19.10 (as we track
mainline in non-LTS releases), but then there would not be a NGINX 1.18
stable available in time for Ubuntu 20.04 to pick up.
I don't know about the NGINX release schedule too much (is it regular and
reliable?), maybe this is not an issue at all, but I have seen similar
issues for other packages so I wanted to mention it.


> ---
> Thomas Ward
> Ubuntu Server Team Member
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam



-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Ubuntu Server development summary - 07 August 2018

2018-08-07 Thread Joshua Powers
Hello Ubuntu Server,

The purpose of this communication is to provide a status update and
highlights for any interesting subjects from the Ubuntu Server Team. If
you would like to reach the server team, you can find us at
the #ubuntu-server channel on Freenode. Alternatively, you can sign up
and use the Ubuntu Server Team mailing list [0].

[0]: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server

## cloud-init

- docs: Fix example cloud-init analyze command to match output.
  [Wesley Gao]
- netplan: Correctly render macaddress on a bonds and bridges when
  provided. (LP: #1784699)
- tools: Add 'net-convert' subcommand command to 'cloud-init devel'.
- redhat: remove ssh keys on new instance. (LP: #1781094)
- Use typeset or local in profile.d scripts. (LP: #1784713)
- OpenNebula: Fix null gateway6 [Akihiko Ota] (LP: #1768547)
- Canonical's Chad Smith is granted PPU rights (per package upload) [1]
  into Ubuntu for cloud-init and curtin packages.

[1]: https://wiki.ubuntu.com/UbuntuDevelopers#PerPackage

## Contact the Ubuntu Server team

- Chat on #ubuntu-server on Freenode
- Email the ubuntu-server mailing list [2]

[2]: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server

## Bug Work and Triage

- 285 in the backlog [3]
- 121 bugs reviewed since the last report
- Notes on daily bug triage [4]

[3]: 'https://bugs.launchpad.net/~ubuntu-server/+subscribedbugs
[4]: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#Bug_Triage

## Ubuntu Server Packages

Below is a summary of uploads to the development and supported
releases. Current status of the Debian to Ubuntu merges is tracked on
the Merge-o-Matic page [5]. For a
full list of recent merges with change logs please see the Ubuntu
Server report [6].

[5]: https://merges.ubuntu.com/main.html
[6]: http://reqorts.qa.ubuntu.com/reports/ubuntu-server/merges.html

### Proposed Uploads to the Supported Releases

Please consider testing the following by enabling proposed [7], checking
packages for update regressions, and making sure to mark affected bugs
verified as fixed [8].

[7]: https://wiki.ubuntu.com/Testing/EnableProposed
[8]: https://wiki.ubuntu.com/StableReleaseUpdates#Verification

Total: 4

- cloud-init, bionic, 18.3-9-g2e62cb8a-0ubuntu1~18.04.2, chad.smith [9]
- cloud-init, xenial, 18.3-9-g2e62cb8a-0ubuntu1~16.04.2, chad.smith [10]
- ipmitool, xenial, 1.8.16-3ubuntu0.2, dannf [11]
- keepalived, xenial, 1:1.2.24-1ubuntu0.16.04.1, corey.bryant [12]

[9]:
https://launchpad.net/ubuntu/+source/cloud-init/18.3-9-g2e62cb8a-0ubuntu1~18.04.2
[10]:
https://launchpad.net/ubuntu/+source/cloud-init/18.3-9-g2e62cb8a-0ubuntu1~16.04.2
[11]: https://launchpad.net/ubuntu/+source/ipmitool/1.8.16-3ubuntu0.2
[12]:
https://launchpad.net/ubuntu/+source/keepalived/1:1.2.24-1ubuntu0.16.04.1

### Uploads Released to the Supported Releases

Total: 7

- clamav, trusty, 0.100.1+dfsg-1ubuntu0.14.04.3, leosilvab [13]
- libapache2-mod-perl2, xenial, 2.0.9-4ubuntu1.1, ahasenack [14]
- libmspack, bionic, 0.6-3ubuntu0.1, leosilvab [15]
- libmspack, xenial, 0.5-1ubuntu0.16.04.2, leosilvab [16]
- lxc, bionic, 3.0.1-0ubuntu1~18.04.2, stgraber [17]
- python-django, bionic, 1:1.11.11-1ubuntu1.1, mdeslaur [18]
- smartmontools, trusty, 6.2+svn3841-1.2ubuntu0.1, ahasenack [19]

[13]:
https://launchpad.net/ubuntu/+source/clamav/0.100.1+dfsg-1ubuntu0.14.04.3
[14]:
https://launchpad.net/ubuntu/+source/libapache2-mod-perl2/2.0.9-4ubuntu1.1
[15]: https://launchpad.net/ubuntu/+source/libmspack/0.6-3ubuntu0.1
[16]: https://launchpad.net/ubuntu/+source/libmspack/0.5-1ubuntu0.16.04.2
[17]: https://launchpad.net/ubuntu/+source/lxc/3.0.1-0ubuntu1~18.04.2
[18]:
https://launchpad.net/ubuntu/+source/python-django/1:1.11.11-1ubuntu1.1
[19]:
https://launchpad.net/ubuntu/+source/smartmontools/6.2+svn3841-1.2ubuntu0.1

### Uploads to the Development Release

Total: 16

- apache2, 2.4.34-1ubuntu1, ahasenack [20]
- bind9, 1:9.11.4+dfsg-3ubuntu1, ahasenack [21]
- cloud-init, 18.3-18-g3cee0bf8-0ubuntu1, chad.smith [22]
- docker.io, 17.12.1-0ubuntu5, mwhudson [23]
- dovecot, 1:2.3.2.1-1ubuntu1, paelzer [24]
- dpdk, 17.11.3-3, pkg-dpdk-devel [25]
- exim4, 4.91-6ubuntu1, ahasenack [26]
- freeipmi, 1.5.7-2ubuntu1, dannf [27]
- ipmitool, 1.8.18-5ubuntu2, dannf [28]
- libnl3, 3.4.0-1, mmind [29]
- nut, 2.7.4-8ubuntu1, dannf [30]
- ocfs2-tools, 1.8.5-5ubuntu1, ahasenack [31]
- open-vm-tools, 2:10.3.0-0ubuntu1, paelzer [32]
- python-django, 1:1.11.15-1ubuntu1, costamagnagianfranco [33]
- python-django, 1:1.11.15-1, None [34]
- unixodbc, 2.3.6-0.1, vorlon [35]

[20]: https://launchpad.net/ubuntu/+source/apache2/2.4.34-1ubuntu1
[21]: https://launchpad.net/ubuntu/+source/bind9/1:9.11.4+dfsg-3ubuntu1
[22]:
https://launchpad.net/ubuntu/+source/cloud-init/18.3-18-g3cee0bf8-0ubuntu1
[23]: https://launchpad.net/ubuntu/+source/docker.io/17.12.1-0ubuntu5
[24]: https://launchpad.net/ubuntu/+source/dovecot/1:2.3.2.1-1ubuntu1
[25]: https://launchpad.net/ubuntu/+source/dpdk/17.11.3-3
[26]: https://launchpad.net/ubuntu/+source/exim4/4

Inquiry: NGINX branch to track in "Interim" Non-LTS Releases

2018-08-07 Thread Thomas Ward
Currently, all LTS versions of Ubuntu that are currently supported have
a version of the NGINX Stable branch in the repositories.  This was done
initially so that we can provide a 'stable' and 'released without new
features' type of branch we would be able to track.  In the cycle before
release, we kept it in line with NGINX Mainline because once NGINX
Stable was cut from that Mainline branch, they'd have newer features
that would otherwise have been unavailable if we had tracked Stable.

My assumption is we want to still do this type of behavior (that is,
track Mainline branch) in interim releases.  This lets the interim
releases of Ubuntu work with newer features that NGINX introduces,
allowing us to file bugs upstream as necessary with the Mainline builds
or to debug issues as they arise in the packaging.  However, because I
am not sure if this is what we wish to do, I thought I'd reach out to
the rest of the Server Team for your input.

What do you think would be best, tracking NGINX Stable, or tracking
NGINX Mainline, for the interim non-LTS releases?  I'm leaning towards
tracking Mainline in the interim releases, if there's no objection -
it'll let users who want more cutting edge NGINX features to use those
in the interim releases without having to force them to use the PPAs.


---
Thomas Ward
Ubuntu Server Team Member

-- 
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam