SRU policy: Allow new features in LTSes under certain conditions

Robie Basak robie.basak at
Wed Sep 2 09:51:37 UTC 2015

Hi Martin,

Could you please provide some clarification on one aspect of your

On Tue, Sep 01, 2015 at 05:45:26PM +0200, Martin Pitt wrote:
>           They must not change the behaviour on existing installations
> (e. g. entirely new packages are usually fine). If existing software
> needs to be modified to make use of the new feature, it must be
> demonstrated that these changes are unintrusive, have a minimal
> regression potential, and have been tested properly.

For clarity, let me call the above requirements "the quality criteria".

Consider a new feature where the proposed LTS update does meet the
quality criteria. Who will decide whether this feature is acceptable to
SRU to the LTS?

Would each proposed feature still need to go individually to the TB for
approval? Or would this new policy give uploaders the ability to add new
features to the LTS directly, since the SRU team would simply approve it
under this new policy?

For example, what should a sponsor do to handle a new feature in the
sponsorship queue? Just upload if it meets the quality criteria, to be
accepted by the SRU team after they have double-checked? Or should extra
steps be taken to determine if we want the new feature in the LTS?



More information about the technical-board mailing list