[gnu.andrew at redhat.com: Re: OpenJDK 8u and Backport Bugs]

[Lindenmaier, Goetz]

Hi,

While I am currently fine with the process, I see some of the points
that were made here.

But the whole downport process will feel a lot different and change 
slightly with the move to github.  We really should only change the 
process once we are all familiar with the new workflows. 
One thing that improves is that the downport issues opened 
automatically will contain as assignee the person that did the 
downport.

Thus I would rather vote for driving the change to github, than
discussing changes that might be pointless after the move.

Anyways, on my side, the overheads are not on the reporting side.
I would like to see the review and approval process slimmed
down.  I was kept busy monitoring changes for review and approval, 
coordinating it with testing and keeping the changes in proper
order instead of discussing potential problems of the changes.
But I don't want to raise this before we are in github.

Just my 5 ct ��

Best, 
  Goetz.



-----Original Message-----
From: jdk-updates-dev <jdk-updates-dev-retn at openjdk.java.net> On Behalf Of Martin Balao
Sent: Donnerstag, 17. Dezember 2020 15:20
To: Langer, Christoph <christoph.langer at sap.com>
Cc: Severin Gehwolf <sgehwolf at redhat.com>; Andrew Hughes <gnu.andrew at redhat.com>; jdk-updates-dev at openjdk.java.net; jdk8u-dev <jdk8u-dev at openjdk.java.net>
Subject: Re: [gnu.andrew at redhat.com: Re: OpenJDK 8u and Backport Bugs]

On Tue, Dec 15, 2020 at 6:11 AM Langer, Christoph
<christoph.langer at sap.com> wrote:
> As for those two points: I can understand them - as specific requirements for your workflow within your company, I guess.

I believe the intention is quite the opposite. Instead of tracking or
assigning backport assignments internally -what we've been doing so
far-, we are proposing a process to do it in the open; so everyone in
the community can participate in the same way. As you well pointed
out, this could be potentially achieved with comments in the main
ticket. However, I see value for every company/organization/individual
in generating automatic reports and tracking overall progress easily
-as Severin said, tracking comments is not feasible-. Again, this
could be achieved with labels; but I agree with Dalvid in not
polluting JBS main-bug tickets -particularly when there is a
'Backports' feature in JBS for exactly that, and we can make more
things explicit in addition to the assignee-.

I'll give you a more concrete example. If we want JDKs to remain
compatible, we need to track bugs for parity. Ideally, this effort
should be distributed throughout the community. We need to be able to
get statistics of the overall progress, not just what we are doing
internally at Red Hat.