[eclipse-dev] Planning Meeting Post-Notes - 2 May 2012

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

This is just a quick follow-up on the many
discussion topics from this call:

1) The branches for the releng git project
will be switched on Tuesday next week. An email will go to eclipse-dev
beforehand with instructions on how to update your local clone once this
happens. For details see: https://bugs.eclipse.org/bugs/show_bug.cgi?id=377235

2) For the pack200 issue, p2 team is
investigating a change to the default settings so we don't have to ask
all clients to change their jar-processor settings. If any action is required
it will be announced here. For details see: https://bugs.eclipse.org/bugs/show_bug.cgi?id=378200

3) We ran out of time on discussion
merging the CBI changes into our repositories before Juno. This mostly
involves adding pom.xml and related metadata to our bundles to allow them
to be built by Tycho. This would make it easier to get Juno-based CBI builds
going. We will revisit this at next week's planning call. Please chime
in if you have strong feelings on this either way.

4) We didn't have time to discuss the
git commit hook change. The short summary is that the proposed changes
give committers more freedom to do what they want in their own topic branches,
while protecting the "main" branches from deletion or non-fastforward
commits. Please review Paul's summary and we'll discuss at next week's
call.

John

Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx>
Sent by: eclipse-dev-bounces@xxxxxxxxxxx

05/02/2012 10:46 AM

Please respond to
"General development mailing list of the Eclipse project."        <eclipse-dev@xxxxxxxxxxx>

To	"General development mailing list of the Eclipse project." <eclipse-dev@xxxxxxxxxxx>
cc
Subject	Re: [eclipse-dev] Planning Meeting Notes - 2 May 2012

Discussion topics:

- merging CBI changes upstream into our real Eclipse repositories
- - mostly consists of pom.xml files at the moment
- - consuming the pom.xml files will reset the qualifiers on most plugins
and fragments
- - If we do it before Juno it will make the last commit timestamp consistent
for plugins that don't change
- - releng contains most changes
- - state of the world: Bug 372792
- Status of CBI build for Eclipse Platform


- Bug 362363
- Better policy ... provide hooks to allow a committer to delete <userid>/branchname
branches
- - eclipse.platform.ui has been running with this pre-receive hook for
a couple of weeks
- - it allows developers to do whatever they want with topic branches of
the pattern committerId/branchName
- - it allows deletes of tags that use the same pattern, committerId/tag
- - it disallows creates, delete, and non-ff merges for branches like master,
integration, R3_development, etc
- - it only allows creates of first level tags.
- - there are properties that can be set on the remote repo to temporarily
allow the operations

We want to roll this out  to the other repos.  This provides
a lot of protection while allowing developers to use git flexibility in
their topic branches.

Later,
PW


-- 
Paul Webster
Hi floor.  Make me a sammich! - GIR_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev