Can I assume that you mean Mars? ;-)
I've started assembling the list of projects/releases that will join
Mars [0]. I'll put you down for 2.2.1 for now; if you do decide to
include a different release with Mars, then let us know on this list
(before the M4 deadline) and I'll update the record.
More generally... participating projects should create a record (if one
does not already exist) for the release that they intend to contribute
in the PMI and then inform the community via this list.
Remember that project plans need to be specified by M4. A minimal plan
that includes a description [1] of the release and a list of issues [2]
(which we can generate automatically) shouldn't be too onerous, I hope.
It would be good if you can capture a theme or two for your plan.
Note that I hope to implement some automagic milestones generation based
on a suggestion from Ed [3].
Let me know if you require assistance.
Wayne
[0]https://projects.eclipse.org/releases/mars
[1]https://wiki.eclipse.org/Project_Management_Infrastructure/Release_Metadata#Description
[2]https://wiki.eclipse.org/Project_Management_Infrastructure/Release_Metadata#Issues
[3]https://bugs.eclipse.org/bugs/show_bug.cgi?id=440708
On 07/30/2014 04:42 AM, Mickael Istria wrote:
Hi all,
SWTBot contributors would like to integrate SWTBot to Luna aggregator,
and to PDE EPP package. Cf discussion
https://dev.eclipse.org/mhonarc/lists/swtbot-dev/msg00618.html
The initial contribution is SWTBot 2.2.1, which was released 4 months
ago:
https://projects.eclipse.org/projects/technology.swtbot/releases/2.2.1
SWTBot features would be added to the "Testing" category.
Since SWTBot depends on GEF, its offset would be +2. However, this
shouldn't have a big impact since SWTBot will not contribute
milestones to aggregator, but only approved releases. SWTBot is stable
and there is very low risk of breaking change in its main APIs. If
SWTBot has to create a new release by May/June 2015, we'll try to
synchronize promotion and announcement with the Luna simultaneous release.
What else needs to be done?
Should I put a Git patch on a bug for cross-project? Still no way to
contribute to simultaneous release with Gerrit? :P
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Wayne Beaton
Director of Open Source Projects, The Eclipse Foundation
<http://www.eclipse.org>
Learn about Eclipse Projects <http://www.eclipse.org/projects>
EclipseCon Europe 2014 <https://www.eclipsecon.org/europe2014>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev