Re: [cross-project-issues-dev] Reminders and notes about upcoming M4

[David M Williams <david_williams@xxxxxxxxxx>]

> Do i need special permission for this ?

Yes. See http://wiki.eclipse.org/Juno/Contributing_to_Juno_Build
<quote>
Check out project org.eclipse.juno.build from
dev.eclipse.org:/cvsroot/callisto. If you do not have write access to this
repository location, contact the webmaster, explaining which project you
are working with, and CC the Planning Council chairperson (currently
david_williams@xxxxxxxxxx) or open a bugzilla entry (with that same
information).
</quote>


> Attached is the patch containing my changes for contribution of EMF
Query2.

If you get in a pinch, I'd be glad to help out, but please provide patches
via bugzilla, cross-project component, for all the usual record-keeping
reasons.

Thanks,





From:	Ashwani Sharma <ashw.kumar@xxxxxxxxx>
To:	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date:	12/05/2011 10:50 PM
Subject:	Re: [cross-project-issues-dev] Reminders and notes about
            upcoming M4
Sent by:	cross-project-issues-dev-bounces@xxxxxxxxxxx



Hi,

I am not able to submit updated files for contribution. I am putting files
here: org.eclipse.juno.build @ /cvsroot/callisto
Do i need special permission for this ?

Attached is the patch containing my changes for contribution of EMF Query2.

Regards,
Ashwani Kr Sharma

On Tue, Dec 6, 2011 at 4:37 AM, David M Williams <david_williams@xxxxxxxxxx
> wrote:


  First, remember M4 is "next week" and is short .... code-done window from
  Friday 12/9 to Wednesday 12/14 ... to be made available on 12/16. Please
  remember to respond quickly to "build breaks", even if before your
  official
  +n due date.

  Second, projects leads, remember to "sign up" for the Juno release by M4,
  on the Eclipse Foundation's Portal. For a list of who is signed up, see
  http://eclipse.org/juno/planning/SimultaneousReleaseOverview.php

  For our M4 composite repo, please note ... normally we keep 3 milestones
  (M-2 to M) in our composite repo .../releases/juno ... but, it is
  anticipated that we will not be able to do that for M4, since a central,
  much used bundle (javax.servlet) will have its package versions moving
  _down_ from previous milestones. While that's been announced before and
  discussed in other bugs, see bug 365629 for complications that might
  arise
  when both versions are "available". So, we will plan on the M4 juno
  common
  repository to be _only_ M4. This might effect anyone with "runtime
  targets"
  defined in their IDEs (forcing some updates to be required sooner than
  the
  M-2 strategy allows). Please let us know if this plan has unanticipated
  effects.

  I have just this evening updated .../releases/staging so that everyone
  who
  has contributed recently (since M3) should be in there ... if you want to
  do some early testing.

  At this moment, 4 projects have "enabled='false'" somewhere still in
  their
  b3aggrcon file ... remember to join-in by M4. Be there, or be square :)

  equinox.b3aggrcon (4 matches)
  mdt-papyrus.b3aggrcon
  rap.b3aggrcon
  scout.b3aggrcon

  Thanks all,



  _______________________________________________
  cross-project-issues-dev mailing list
  cross-project-issues-dev@xxxxxxxxxxx
  https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[attachment "EMFQuery2JunoContribution.txt" deleted by David M
Williams/Raleigh/IBM] _______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev