I have my usual concern that not all projects are paying attention.
PMC representatives, please check in with your projects to ensure
that they have at least one committer subscribed to this list. I'll
include a reminder in the note to the member-committers list that
I'm planning to send out this afternoon.
I've modified the generated release page [1] a bit. It now includes
a list of projects "dropped in this release".
The list currently includes the following projects:
Agent Modeling Platform
EMF Query
EMF Transaction
EMF Validation
Extended Editing Framework (EEF)
Graphical Modeling Framework (GMF) Notation
Graphical Modeling Framework (GMF) Runtime
EclipseLink Project
BPEL Designer
SCA Tools
Koneki
Maven Integration
Maven Integration for Web Tools Platform
Eclipse Packaging Project
Marketplace Client
Target Communication Framework
PHP Development Tools
Target Management
A link to the participation instructions are included on the page.
I eagerly await your concern with my use of the word "dropped".
Wayne
[1]
https://projects.eclipse.org/releases/luna
On 12/12/2013 01:46 PM, David M
Williams wrote:
To add some reminders to Wayne's
...
Remember the "window" between +0 and
"availability"
is now reduced to one week instead of two, which means all
contributions
must be "in the build" by Wednesday, 12/18.
As of right now, the following projects have
something
disabled in their contribution files:
contribution as a whole is not enabled:
amp.b3aggrcon
pdt.b3aggrcon
soa-sca.b3aggrcon
one or more features or repositories are not
enabled:
dltk.b3aggrcon
riena.b3aggrcon
sphinx.b3aggrcon
Please get everything "enabled" ... or,
I know, some of you (such as amp, I believe?) was considering
not being
in Sim. Release. So, good time to confirm your plans
explicitly.
I am most concerned about "PDT", as I believe
they are proposing to "restore" a PHP Package in EPP? ... if
so, more important than usual to "get in early". Feel free to
correct any errors in my memory.
And a reminder to all, you do not have to wait
to
your exact +n day to provide a "warmup" build ... even if you
submit your final bits on your +n day. This often helps find
issues "downstream"
from you that no one is aware of yet and is less stressful to
know about
"early".
Not to mention, it allows some "early testing"
of .../releases/staging to make sure what you think you are
contributing
is actually "getting in" the aggregation repository.
I have contributed the M4 candidate Platform
bits
to b3aggr files, and while the job is still running, will
promote those
to staging soon. (And, will finalize tomorrow, Friday,
afternoon, after
all final testing and sign-offs are obtained).
Much thanks,
From:
Wayne Beaton
<wayne@xxxxxxxxxxx>
To:
Cross project issues
<cross-project-issues-dev@xxxxxxxxxxx>,
Date:
12/11/2013 03:47 PM
Subject:
[cross-project-issues-dev]
Luna
M4: The opt-in deadline approaches
Sent by:
cross-project-issues-dev-bounces@xxxxxxxxxxx
Greetings folks.
Luna M4 is on December 20/2013.
Projects are required to opt-in by that date. As of this moment,
I have
56 projects on my list [1]. I'm pretty sure that I'm missing
around 20
participants from last year. Opt-in instructions are in the wiki
[2]. Note
that your PMC will have to appeal on your behalf if you do not
opt-in before
the deadline.
Participating projects must also have a well-formed project plan
by this
date. I encourage projects to use the release record metadata
[3] to capture
plan information, including a short (2-3 sentence) description
of the release,
milestones, and at least a couple of themes. Note that you can
attach Bugzilla
queries [4] to individual themes.
If you do choose to use the old school XML-style plan format,
please at
least provide a description in the release metadata. I'll use
this information
when I generate a "what's in Luna" page. If we do a good job
of this, it will be a tremendous help to the marketing folks
when the time
comes to start marketing the cool and exciting features in the
release.
Keep the description concise. No bullets.
FWIW, project and release metadata can be edited by any project
member,
or member of the associated PMC. So PMC members, you can make
minor edits
as needed.
By way of reminder, the release cycle and review process is
captured in
the wiki [5].
Thanks,
Wayne
[1] https://projects.eclipse.org/releases/luna
[2] http://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#State_intent_early_.28M4.29
[3] http://wiki.eclipse.org/Project_Management_Infrastructure/Release_Metadata
[4] http://wiki.eclipse.org/Project_Management_Infrastructure/Release_Metadata#Bugs_as_Plan_Items
[5] http://wiki.eclipse.org/Development_Resources/HOWTO/Release_Cycle
--
Wayne Beaton
Director of Open Source Projects, The
Eclipse Foundation
Learn about Eclipse
Projects
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|