Dear Ernesto,
1/ The Ref mapping should be : HEAD:refs/for/master
2/ If you use Gerrit to share your contribution, you probably won’t need to use a custom branch for your bug.
3/ Most probably yes : the same password. You may also authenticate with SSH keys that you set in your Gerrit profile
settings and then use "ssh://USERNAME@xxxxxxxxxxxxxxx:29418/papyrus/org.eclipse.papyrus" as repo URL.
Best regards.
Florian
De : mdt-papyrus.dev <mdt-papyrus.dev-bounces@xxxxxxxxxxx>
De la part de Ernesto Posse via mdt-papyrus.dev
Envoyé : mardi 20 février 2024 23:58
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Cc : Ernesto Posse <eposse@xxxxxxxxx>
Objet : Re: [mdt-papyrus.dev] Bug 582940
Hi, I’m following up with my questions last week about submitting a patch to Gerrit. See the questions below. I’d like to know if I have configured Gerrit correctly as I don’t want to mess up the repo.
Thanks
1) When configuring the local branch for push, I set the remote and push remote to the newly created remote (which I called gerrit), but should I change the upstream branch? The default is set to refs/head/master. I don’t want to mess
any master branch!
2) Is there a convention for naming branches? I see a lot of “bugs/NNNNNN-short-description. That’s what I’ve used. Is that ok?
Hi Ansgar,
I was wondering about pushing to Gerrit, because our company is no longer an Eclipse member and my understanding was that it means I am no longer an Eclipse Committer, but in Bugzilla I see my messages with an ECA tick mark, so I guess
I might still be able to push? I’ll give it a try.
As for the future plans, when is the move to Papyrus-Sirius and Papyrus web planned for? Is it for version 7.0? Or later?
Dear Ernesto,
good to hear from you after quite some time!
Concerning the bug, you should still be able to push to gerrit. I don't think, that required to put the general text (I wrote the code ...) in the commit message as it is not very useful when looking at the history. Make sure, a reference to the bug is in
the header of the modified files.
I also like to point out that the architectural framework of "classic" (GMF, XWT) Papyrus will not be used in the long run. The successors Papyrus-Sirius and Papyrus Web use different customization mechanisms.
Best
Ansgar
On 15/02/2024 04:05, Ernesto Posse via mdt-papyrus.dev wrote:
I’ve submitted a new bug report to Bugzilla, Bug 582940, but I accidentally cut the first few paragraphs with the bug
description when I pasted it in the Comment textbox. So I’ve added the full description as a new comment, as I cann’t edit my previous comment.
I’ve also added a full diagnosis of the bug and can submit a patch, but I don’t think I can push it to Gerrit as I am no longer an Eclipse Committer. Should I use a particular patch header
when creating the patch?
Also, according to the guidelines, I should add messages stating that I wrote the code, that it has no cryptography, etc. Where do I write those? In a local git commit comment and then
create the patch from that commit?
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mdt-papyrus.dev
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/mdt-papyrus.dev
|
