I would like “training” on this as well, I’m interested in not only our use for Eclipse purposes, but also more generally, especially for improving practices
for application software engineers using Eclipse PTP for their work – (could become another module in our tutorial suite).
From: ptp-dev-bounces@xxxxxxxxxxx [mailto:ptp-dev-bounces@xxxxxxxxxxx]
On Behalf Of Beth Tibbitts
Sent: Thursday, June 20, 2013 10:03 AM
To: Parallel Tools Platform general developers
Subject: Re: [ptp-dev] Gerrit
Can we have some 'training' and have some suggested workflows and ways to do things so that everyone learns how to do it the same way?
On Thu, Jun 20, 2013 at 7:04 AM, Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
Roland,
I'm ok with this. I think initially I'd like to keep the repo open for direct commits. Once we get used to using gerrit we can revisit make reviews mandatory.
Please open the bug.
Greg
On Jun 19, 2013, at 10:08 PM, Roland Schulz <roland@xxxxxxx> wrote:
> Hi,
>
> could we enable Gerrit for PTP:
http://wiki.eclipse.org/Gerrit? The
> only effect for committers is that they need to update their git url
> for fetch/push once. Otherwise all git operations would stay the same.
> The advantage would be that we could have contributors upload patches
> directly from git (no need to make patches and upload them manually to
> bugzilla). Also it would allow any committer (who wishes to use it) to
> use it for code review. E.g. John and me like to do code review at
> least for important commits and currently we need to do that
> externally (we use github).
>
> Roland
>
> --
> ORNL/UT Center for Molecular Biophysics
cmb.ornl.gov
> 865-241-1537, ORNL PO BOX 2008 MS6309
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
--
