[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [glassfish-dev] Release notes and Issue tracking
|
CI task would be good. Does anybody have the skills for that?
-----Original Message-----
From: glassfish-dev-bounces@xxxxxxxxxxx <glassfish-dev-bounces@xxxxxxxxxxx> On Behalf Of sawamura.hiroki@xxxxxxxxxxx
Sent: 24 March 2020 12:35
To: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>
Subject: Re: [glassfish-dev] Release notes and Issue tracking
I think it's a simple and effective idea. +1
> Every PR must have an associated issue(s) and a comment like “fixes #xxx” referring to the issue(s).
If possible, we should add a GitHub CI task to check if a PR is associated to the issue (like the eclipsefdn/eca) because it's likely to be forgotten.
Hiroki
From: glassfish-dev-bounces@xxxxxxxxxxx <glassfish-dev-bounces@xxxxxxxxxxx> On Behalf Of Steve Millidge (Payara)
Sent: Tuesday, March 24, 2020 7:50 PM
To: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>
Subject: [glassfish-dev] Release notes and Issue tracking
All,
Bill raised a question on generation of release notes. Typically this would be done via the issue tracker. Given we are using GitHub as our issue tracker I’m suggesting we generate issue notes from there.
So I’m proposing the following process. Every PR must have an associated issue(s) and a comment like “fixes #xxx” referring to the issue(s).
Each issue can be assigned to the appropriate milestone release.
We can therefore generate our release notes from the milestone. See https://github.com/eclipse-ee4j/glassfish/issues?q=is%3Aopen+is%3Aissue+milestone%3A6.0.0
Thoughts?
Steve
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev
