| [cross-project-issues-dev] Declare intent to participate in Oxygen |
|
Greetings folks. I believe that I've gotten my list of participating projects [1] up-to-date with those projects that have used this list to declare their intent to participate in the Oxygen Simultaneous Release. I also added a few projects that participated in Neon and had created release records dated June 28/2017 on an assumption that by bothering to create the record for the release they could reasonably be understood to be "paying attention". If you have not yet formally declared intent, please do so (this
will get you off of the inappropriately labeled "Dropped in this
Release" list hidden in the Overview block). If you project is on that list but does not have a version number
beside it, that means that you either did not create a release
record or that I could not identify it. If you have not yet
created a release record for your Oxygen release, please do so at
your earliest convenience. Placeholder release records are fine. Ideally, however, it would
be very helpful if you can provide an "executive summary" for the
release in the description field. Note that there is no value in
stating that the release is part of Oxygen in the executive
summary; I'm looking for a few words describing the main areas of
development focus or cool new features. While I have your attention, I'd like to take a run at building
an aggregate change log for the release (see Bug 488598 [3]) and
am of the mind that the easiest way to do this consistently is to
leverage the technology that underlies the "issues" tab that
already exists in the PMI [4]. If you name your target milestones
in Bugzilla, your project will automatically participate in this.
Thanks! Wayne [2] https://projects.eclipse.org/releases/oxygen/details [3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=488598 [4] https://www.eclipse.org/projects/handbook/#pmi-release-issues --
Wayne Beaton @waynebeaton The Eclipse Foundation |