eclipse-dev

Re: [eclipse-dev] All Components: please apply CBI patches

pwebster@xxxxxxx (Paul Webster) — Tue, 22 May 2012 11:11:48 GMT

On Mon, May 21, 2012 at 4:05 PM, Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx> wrote:

In our prep work to support the Eclipse FoundationÂ CBI initiative, the CBI folks have prepared commits so we can accept their pom.xml file changes upstream.

BugÂ379747 - Pull request for Platform from CBI
BugÂ379748 - Pull request for Equinox from CBI
BugÂ379749 - Pull request for PDE from CBI
BugÂ379750 - Pull request for JDT from CBI

Addendum:

#1. Component leads should check the blocker bug for each project, to review non-pom-file changes applicable to their repos (usually build.properties, manifests, or tests).Â Apply them if they can be consumed, or ask questions about them on the bugs.Â PDE doesn't require any non-pom-file changes.

#2. If cherry-picking the change, you can add the remote and fetch the appropriate branch.Â This uses the eclipse.platform.ui repo as an example, and I get the branch name for the fetch from the URL to the commit:

git remote add cbi git://git.eclipse.org/gitroot/cbi/eclipse.platform.ui.git # for platform ui
# you can do a git fetch cbi, but that will create all of the remote branches under cbi/
# this only gets the one we're interested in
git fetch cbi refs/heads/R3_cbipoms:refs/remotes/cbi/R3_cbipoms
git log cbi/R3_cbipoms

git cherry-pick

I have EGit instructions if anyone would like them

PW

--
Paul Webster
Hi floor.Â Make me a sammich! - GIR

[eclipse-dev] All Components: please apply CBI patches

pwebster@xxxxxxx (Paul Webster) — Mon, 21 May 2012 20:05:39 GMT

In our prep work to support the Eclipse FoundationÂ CBI initiative, the CBI folks have prepared commits so we can accept their pom.xml file changes upstream.

BugÂ379747 - Pull request for Platform from CBI
BugÂ379748 - Pull request for Equinox from CBI
BugÂ379749 - Pull request for PDE from CBI
BugÂ379750 - Pull request for JDT from CBI

Each component lead should look at the bugs for their projects, and apply the commits listed in the above bugs.Â You can either add the CBI forks as remotes in your local git repo and cherry pick the commit or take a patch from the web page.

They can go in any time now, but should be completed before tomorrow's (Tuesday evening) I build.

--
Paul Webster
Hi floor.Â Make me a sammich! - GIR

[eclipse-dev] Eclipse and Equinox Juno RC1 now available

david_williams@xxxxxxx (David M Williams) — Sat, 19 May 2012 22:46:24 GMT

p2 repo
http://download.eclipse.org/eclipse/updates/4.2milestones

Eclipse Downloads
http://download.eclipse.org/eclipse/downloads/drops4/S-4.2RC1-201205182145/

Equinox Downloads
http://download.eclipse.org/equinox/drops/S-3.8RC1-201205182145/

Re: [eclipse-dev] Planning Meeting Notes May 16, 2012

david_williams@xxxxxxx (David M Williams) — Wed, 16 May 2012 15:00:11 GMT

Sorry to be late with my status/discussion notes:

releng
status For RC1,
still one issue to complete equinox download page fix
not sure test automation is working as desired?

Discussion:
For "build notes", do we want to remove them completely? Or leave up to each team to remove, or keep current?
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=364078
Build schedule for remaining RCs? Saturday, Sunday, Monday, Tuesday Wednesday? 7 PM and 9 PM?

Michael Rennie ---05/16/2012 10:42:56 AM---Discussion Topics - None

From: Michael Rennie
To: "General development mailing list of the Eclipse project." ,
Date: 05/16/2012 10:42 AM
Subject: [eclipse-dev] Planning Meeting Notes May 16, 2012
Sent by: eclipse-dev-bounces@xxxxxxxxxxx

Discussion Topics
- None

SWT
- various 3.8/4.2 RC1 bug fixes
- released launcher on Windows with support for large icons
- tested recent WebKitGTK 1.8 release, appears to have only introduced one problem
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=379446 (fixed)
- CBI: will investigate changing tag names going forward

Debug
- Inbox triage
- No remaining work items for RC1

Ant
- No remaining work items for RC1

PDE
- Inbox triage
- Investigating one remaining performance bug for RC1 (https://bugs.eclipse.org/365846 )

Michael Rennie_______________________________________________ eclipse-dev mailing list eclipse-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://dev.eclipse.org/mailman/listinfo/eclipse-dev

[eclipse-dev] Planning Meeting Notes May 16, 2012

Michael_Rennie@xxxxxxx (Michael Rennie) — Wed, 16 May 2012 14:36:40 GMT

Re: [eclipse-dev] Enabled Pre-Receive Hook

pwebster@xxxxxxx (Paul Webster) — Tue, 15 May 2012 13:25:10 GMT

On Tue, May 15, 2012 at 3:20 AM, Daniel Megert <daniel_megert@xxxxxxxxxx> wrote:

Hi have enabled the pre-receive hook on almost all of our repositories (exceptions are platform.swt, platform.resources and jdt.core where I don't have commit rights). Let me know if you experience unexpected things.

I've added a section on our pre-receive hook to http://wiki.eclipse.org/Platform-releng/Git_Workflows#Branches_in_our_Platform_Repos

Work was done in:
BugÂ362363 - Better policy ... provide hooks to allow a committer to delete /branchname branches

--
Paul Webster
Hi floor.Â Make me a sammich! - GIR

[eclipse-dev] Enabled Pre-Receive Hook

daniel_megert@xxxxxxx (Daniel Megert) — Tue, 15 May 2012 07:20:20 GMT

Hi have enabled the pre-receive hook on almost all of our repositories (exceptions are platform.swt, platform.resources and jdt.core where I don't have commit rights). Let me know if you experience unexpected things.

Dani

[eclipse-dev] Copyright updates

John_Arthorne@xxxxxxx (John Arthorne) — Fri, 11 May 2012 14:08:17 GMT

This is a reminder for Eclipse project committers that now is a good time to be updating the copyrights on your source code, if you haven't already done so. This is often left until the end, but in past years we had some last minute problems due to copyright changes in RC3+, so it's safer to get the changes in early in the end game. You don't need a reviewer because it is just a comment change, but please check the changes yourself to make sure the copyright tool behaved properly.

Thanks to Tomasz Zarna we now have a copyright tool that works with Git. You'll need the latest Releng Tools plugin from 3.8 M7 or greater.

John

[eclipse-dev] Planning Meeting Notes - 9 May 2012

Curtis_Windatt@xxxxxxx (Curtis Windatt) — Wed, 09 May 2012 14:47:40 GMT

Planning Meeting Notes
9 May 2012

Discussion topics:
1) Please send status next week to Michael Rennie
2) What should build schedule be?
3) Does ANYONE (besides David) like unique names (date/time) in milestone/release zip files? (bug 378711)

SWT
- M7 test week went well
- Solaris-x86 machine is back, can compile our libraries on it again
- investigating loading of .png images from .ico files on Windows
- RC1 bug fixing

PDE
- RC0 test pass went well
- RC1 bug fixing (4 bugs being considered)
- Fixing documentation

Ant:
- inbox triage
- nothing planned for RC1

Debug:
- inbox triage
- one item planned for RC1 so far (https://bugs.eclipse.org/378040)

Releng:
fixing builds
fixing test running
doing Juno aggregation

Re: [eclipse-dev] Notice of a (quickly) coming change to our map file branches: Today, 5/8, 3 to 4 PM Eastern

pwebster@xxxxxxx (Paul Webster) — Tue, 08 May 2012 19:17:27 GMT

If you do have eclipse.platform.releng.maps.git checked out you can either delete and re-clone your repo *or* you must reset your branches (do not pull).

If you had master checked out you need:

git fetch
git checkout master
git reset --hard origin/master
git checkout R3_development

If you had R4_HEAD checked out:

git fetch
git checkout master
# if you have ever checked out master you must reset it, not merge:
git reset --hard origin/master
git branch -d R4_HEAD

--
Paul Webster
Hi floor.Â Make me a sammich! - GIR