Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [glassfish-dev] Release notes and Issue tracking
  • From: "sawamura.hiroki@xxxxxxxxxxx" <sawamura.hiroki@xxxxxxxxxxx>
  • Date: Tue, 24 Mar 2020 12:34:50 +0000
  • Accept-language: ja-JP, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=fujitsu.com; dmarc=pass action=none header.from=fujitsu.com; dkim=pass header.d=fujitsu.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4AX6HVrC5haVnbQZkf1N1jaqImpEBUIoiNyTSKYqf+E=; b=HohNGrulcLb5Af0Nj7Cxdd1NMWpe6HLDunf3QRvx7hiXQfuXGLojJMsVbKUtvpdiDWvMxezxGnhUX4l7Twx1QjNZqFlHdBVacSlbqa8qMKpzSKR1hGZdfsF+OfocvDd6lGJV2OdO5mOwcHjgaSbVpXUaPfHaaJsOx/NpWcWzLRlRzy0A+IOtEkray2ijwd8GtOJsOb7kIVXCnA7G6b0YeMAJiw3gg9FTuUe7hBdkXZphvhjJx7UVn91wnJGT7vcW98g8KmdNtwnNyPiR4SsEiL7svij2gehojWtqiHHB7LVJmWn51faIavzLkU9SpjDujBJJ/KN3ubuTaiDs/HYVBA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=eQOHWo34C0yVHjWUZEFcrw2RfO7NgFnm9yQst776WwuAgRSPRAgTn0ONYdlPLGJBRQ4IBmLH5Bp2Jdw5MNKhhxbvtTXNlaXK2197idszZamGaQUVq0w/TOAn8qIOO0FUsxBPyqXEr60gBBBKmq7ZXq6uGMo3rdD/nnOZJBxIiZ2VDShGPdeigaHg4OG9NRtHYe7iyX+CAUuEIYpEjc+aHFde3NwDtDYLGBvyWGzqVDT3FvRLl1pKQT8hU9DN/DVJz46s6D8jeY84OnT5YzU+63kha5m6adbTU8+/d8kb+HNXMB6jBpka/oG5OikVLlWqKg7PMQ2W+1UKM8quWLbpkg==
  • Delivered-to: glassfish-dev@xxxxxxxxxxx
  • Ironport-sdr: GX1XD/Qbq+1OgcEUUfpASLvA4SM0JMyZlsqOwDIdS2HcBmjlXHENhkZXDvMownDAd4Z7Q4GW3g 9daWDQfWWTecUvA0mmNUDQY09K5/4U5brniXv+eppF1ytXDrKACxPlpQw5rORRH8RVU43xSdrM d3nDWpmevmm/rkVHPwzYgzlMSQZEe97hbBCP+HwwlqCi25dHUF995aiG7XIoUE7X17ojqXKEmq eAQRAGGtkD4BoOwW623WKuZYGXIVsIIxF71EGl7fnPwpAvrCp6iT7ENwuJ7SPtW6gscJYBepmR u0E=
  • List-archive: <https://www.eclipse.org/mailman/private/glassfish-dev>
  • List-help: <mailto:glassfish-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/glassfish-dev>, <mailto:glassfish-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/glassfish-dev>, <mailto:glassfish-dev-request@eclipse.org?subject=unsubscribe>
  • Thread-index: AdYByV4xnVxVObKeT5yVllilMKMNTgADOZyA
  • Thread-topic: 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

Back to the top