[Bug 536429] Centralize the full (as much as possible) tracking of release process on 1 single page (like a bugzilla issue)
| Bugzilla Link | 536429 |
| Status | NEW |
| Importance | P3 enhancement |
| Reported | Jun 28, 2018 11:54 EDT |
| Modified | Jul 03, 2019 14:59 EDT |
Description
One time-consuming thing when applying the release process defined by EDP is that the current implementation requires to get to diverse channels to perform this process.
We should try to simplify this by keeping a single source of communication. Something like Bugzilla seems great; so we could track the whole process, including require PMC approval (that typically happen by request on the PMC mailing-list) on the same Bugzilla entry that would give a better overview of the state of the release and what's still to do.
Activity
assigned to @epoirier
added bugzilla legacy projects.eclipse.org labels
(In reply to Alexander Kurtakov from comment #1)
As a PMC member - the mailing list approval is really uneffective and error prone, it's way to easy to miss some project's request.
What do you recommend as an alternative?
PMC members can, for example, create a query to search for outstanding release reviews in Bugzilla.
e.g.
(add a resolution=FIXED constraint to that and it will be more useful)
I suppose that I could make a web page that does this for you if that would be valuable.
By Alexander Kurtakov
(In reply to Wayne Beaton from comment #2)
(In reply to Alexander Kurtakov from comment #1)
As a PMC member - the mailing list approval is really uneffective and error prone, it's way to easy to miss some project's request.\
What do you recommend as an alternative?\
PMC members can, for example, create a query to search for outstanding release reviews in Bugzilla.\
e.g.\
https://bugs.eclipse.org/bugs/buglist. cgi?classification=Eclipse%20Foundation&component=Proposals%20and%20Reviews&l ist_id=17665644&product=Community&query_format=advanced&short_desc=%5Brelease %5D%20ecd.&short_desc_type=substring\
(add a resolution=FIXED constraint to that and it will be more useful)\
I suppose that I could make a web page that does this for you if that would be valuable.
In my dreams there is a page under e.g. https://projects.eclipse.org/projects/tools with all reviews, CQs and other actions pending on PMC members to react :) .
(In reply to Alexander Kurtakov from comment #1)
As a PMC member - the mailing list approval is really uneffective and error prone, it's way to easy to miss some project's request.
The scope of the audience is different for the mailing list and bug reports. One benefit of having the approval discussion in the mailing list is broader dissemination and greater transparency.
Another benefit is that in order to post to a request for approval to the PMC list, the project team representative (typically, but not always the PL) would have to actually be a subscriber to that list. Having project teams hooked into the PMC is a good thing, IMHO.
(In reply to Alexander Kurtakov from comment #3)
In my dreams there is a page under e.g. https://projects.eclipse.org/projects/tools with all reviews, CQs and other actions pending on PMC members to react :) .
I've been tinkering with some tools, e.g.
https://eclipse.org/projects/tools/report.php?id=tools
Having a page like you describe seems pretty doable. That might help to solve the problem of missed emails (we're all buried in emails so missing some of them is bound to happen), but only when PMC members proactively look. I'm pretty sure that an email-based notification is required one way or another.
IMO, what would be best would be
- When creating a review, a bugzilla is automatically created and link to review BZ is shown on the release page, while link to release record is shown on bugzilla. This bugzilla automatically adds as CC the project lead.
- a week before release (if this is the value defined in the EDP, or at a better time, a mail titled "PMC, please review release for SuperProject 1.2.3" is automatically sent to the PMC with the link to the Bugzilla, and invites PMC to vote on the review. At the same time as it sends the mail, it could set the "review" fields of the Bugzilla entry to the PMC members so they get a Bugzilla notificiation as well.
With that, as a project lead/releng, I don't have to think about requesting PMC which, in case I forget, leads to a slower review (by my fault, sure, but still slower than it could be with more automation).
I guess PMC members can also enjoy the automatic notification on mailing-list and from bugzilla.Decoupling this one from bug 496321. This is about implementation of the process. The EDP does not define any such implementation.
Maybe it's worth moving this to the PMI?
added to epic &14 (closed)
added statetodo label
We're doing all tracking using a single GitLab issue.
Further, we're moving away from doing release reviews at all in favour of progress reviews which are initiated by the EMO eclipsefdn/emo-team/emo#1 (closed)
I think that the spirit of this request is being met, so I'm going to close it.
As a general comment... I am in favour of automating the things that should be automated. However, I can envision no scenario where we entirely automate away the project team's engagement in governance as defined the Eclipse Foundation Development Process (and operationalised by the EMO). That is, requiring project team engagement in aspects of the governance is a feature, not a bug. Getting a committer to engage with the PMC to request review and approval of review documentation is intentional: it establishes a direct line of communication to ask and answer questions regarding the specific issue at hand, and encourages/forces a ongoing line of communication between the project team and the PMC.
removed statetodo label
removed legacy label
removed bugzilla label
removed projects.eclipse.org label
