| Re: [epp-dev] giving EPP package maintainers committer status on EPP |
What happened with this? Do we have to do something to be able to commit to the epp project that we are the tester/maintainer for?
I seem to remember seeing some email go by about this but now can't find it.
I tried to update epp-parallel earlier this morning but couldn't.
I'm not complaining...just want to help Markus by not relying on him for everything (that he does so wonderfully well) if I don't need to.
...Beth
Beth Tibbitts
Eclipse Parallel Tools Platform http://eclipse.org/ptp
IBM STG - High Performance Computing Tools
Mailing Address: IBM Corp., 745 West New Circle Road, Lexington, KY 40511
Markus Knauer ---05/05/2011 11:26:17 AM---Hi package maintainers, another idea that I discussed with some people at EclipseCon...
From:
Markus Knauer <mknauer@xxxxxxxxxxxxxxxxx>
To:
EPP Developer Mailing List <epp-dev@xxxxxxxxxxx>, Markus Tiede <Markus.Tiede@xxxxxxxxx>, Andreas Hoegger <Andreas.Hoegger@xxxxxxxxx>, Matthias Zimmermann <Matthias.Zimmermann@xxxxxxxxx>
Date:
05/05/2011 11:26 AM
Subject:
[epp-dev] giving EPP package maintainers committer status on EPP
Sent by:
epp-dev-bounces@xxxxxxxxxxx
_______________________________________________Hi package maintainers,
another idea that I discussed with some people at EclipseCon...
>From the package maintainers there are complaints such as 'you
[Markus...] forgot to apply this patch', or 'why can I not change this
small thing myself'. The reason is very simple: You are not a
committer on the EPP project.
<history>
In the early days of EPP this wasn't an issue at all. Years ago, that
means long before p2, there was a single XML file that contained the
package definition. And these XML files were spread on several places
within the eclipse.org CVS. Before every release this caused problems
because I had to create patches and I had to ask the package
maintainers to apply these patches. Especially in the days or on the
weekend before a release this was too time consuming.
When we moved to the p2 director and to the feature+plugin package
definition, I decided that everything has to stay in the EPP CVS and
the package maintainers send their changes in via Bugzilla. As we all
know this is not the best solution, but at least I am able to make
some necessary last minute changes and can try to keep the packages
consistent.
</history>
My proposal is now that we introduce an EPP committer-ship for a
package maintainer in a way very similar to Orbit.
Prerequisite one: The new package maintainer is already committer on
another project that contributes to this package and it sounds
plausible that (s)he will be maintaining the package in the future.
Prerequisite two: The package is more important than the committer...
what I mean with this is that it must be easy to replace an existing
package maintainer / committer by another, new package maintainer.
Sometimes assignments change and it is important to give someone else
the chance to take over the package.
I will go on doing changes for all packages in the future and will try
to fix build errors, but I am sure that you don't need me for the many
small changes, version updates, dependency updates, etc.
First of all I'd like to get your opinion. If there are not too many
protests I will start the new committer process for the existing
package maintainers soon.
Regards, Markus
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev
###
EclipseSource Group
Telefon: +49 721 664733-0 (GMT +1)
Telefax: +49 721 66473329
http://eclipsesource.com
Innoopract Informationssysteme GmbH
Stephanienstrasse 20, 76133 Karlsruhe Germany
General Manager: Jochen Krause
Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883
