Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] EE4J Project Bugzilla

I'm all for consolidation, but I have a couple of questions, that immediately come to mind:

  • Is there ever a need for issues that are not public?
  • Would it be useful (or possible), to leave a pointer in BugZilla to the related GitHub repository (as opposed to outright removal)?
  • Are there other Eclipse process tools or requirements that will be expecting BugZilla products? (if so, can they reliably redirect to the respective GitHub JIRA?)

There is a "one to at least one" mapping between projects and GitHub repositories so, issue mapping may not be immediately apparent. (Eclipse GlassFish being the most extreme on this scale, but the Jakarta EE Stable APIs project is also a grab-bag type project.)

If these are all considered and the consensus is still proceed, great, go for it.

-- Ed

On 3/29/2019 10:03 AM, Steve Millidge (Payara) wrote:

+1

 

From: ee4j-pmc-bounces@xxxxxxxxxxx <ee4j-pmc-bounces@xxxxxxxxxxx> On Behalf Of Wayne Beaton
Sent: 29 March 2019 17:02
To: EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>
Subject: [ee4j-pmc] EE4J Project Bugzilla

 

Hey PMC members.

 

I noticed that the webmaster provisioned Bugzilla products for many of the EE4J Projects. I'm pretty sure that, other than EclipseLink and Eclipse Yasson, none of the projects are actually using them (note that, I'm taking steps to fill the apparent gap in our process that caused this to happen).

 

The full list of Bugzilla records created against EE4J projects other than EclipseLink and Eclipse Yasson is here.

 

There are a handful of security issues reported there. I'm moving them to the "Vulnerability Reports" component, adding project leads in cc, and marking them as "committers only" to reduce the level of disclosure while they are addressed.

 

I'm pretty sure that we'll be left with a bunch of empty Bugzilla products that will serve only to confuse the community (as most of the projects are using GitHub Issues, and probably don't even know that this is here).

 

Unless there is any objection, I'm going to open a bug to request that Webmaster remove the Bugzilla presence for all but EclipseLink and Eclipse Yasson.

 

Note that Bugzilla is available as a means of capturing and managing the disclosure process with some discretion (it provides the ability to temporarily hide issues, while GitHub Issues does not).

 

Any concerns?


Wayne


--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.


_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc

Back to the top