CSR approval process for backports
david.holmes at oracle.com
Mon Dec 10 07:44:12 UTC 2018
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 updates
More information about the csr-discuss