CSR approval process for backports
Joseph D. Darcy
joe.darcy at oracle.com
Wed Dec 12 00:20:50 UTC 2018
My general guidance for backports has always been "don't create the
backport before you need it." Often that means letting the hgupdater
daemon create one on your behalf when you push. At other time, when
administrative approval are needed ahead of time, the backport can be
created manually or via a script.
A CSR should be created off of a backport; a backport should not be
created from a CSR request. If that is possible now, we will look to
remove that capability in a JBS update.
On 12/9/2018 11:44 PM, David Holmes wrote:
> Hi Paul,
> On 8/12/2018 3:02 am, Hohensee, Paul wrote:
>> Would it perhaps be better to create a manual backport issue for the
>> CSR first, get that approved, then follow the normal process for the
>> backport itself?
> Although JBS seems to allow it, as I understand it a "backport" issue
> is expected to be associated with a "bug" or "enhancement" not a "csr
> request". It's not at all clear the expected relationships would be
> created if you did it the way you suggest.
> cc'd crs-discuss for furtehr comment.
>> On 12/6/18, 1:26 PM, "jdk-updates-dev on behalf of David Holmes"
>> <jdk-updates-dev-bounces at openjdk.java.net on behalf of
>> david.holmes at oracle.com> wrote:
>> The updates wiki pages states:
>> "If a change requires CSR approval, that approval must be
>> obtained prior
>> to making the push approval request."
>> but the CSR approval process for a backport is not defined
>> anywhere as
>> far as I can see. After discussion with the CSR Group lead it
>> seems the
>> expectation is that a manual backport issue must be created
>> first, and
>> then a CSR for that backport can be created. can this
>> information be
>> added to the updates page and/or the CSR FAQ and linked from the
More information about the csr-discuss