Hi,
I created
https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/blob/master/DeveloperGuide.md based on my experiences. Please let me know if this helps.
Thanks
Sravan
From: jdt-dev <jdt-dev-bounces@xxxxxxxxxxx>
On Behalf Of Jayaprakash Arthanareeswaran
Sent: 16 March 2022 13:43
To: Eclipse JDT general developers list. <jdt-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: [jdt-dev] Foundation Code and Issue services reminder
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
|
This message came from outside your organization.
|
|
|
ZjQcmQRYFpfptBannerEnd
Thanks, Mikael, for the reference.
> Don't expect anyone to duplicate and maintain all that info into another location, just use existing reference doc.
I don’t think anyone here wants that. Just that I have no recollection of seeing this section before. I always had to refer to
the Github documentation whenever required. Having gone through the GitHub help and noticing that there are different
ways of doing same thing, I tend to think that the existing committers might need some documentation like we have now in
JDT to help them transition and new ones will need some guidance on recommended way of doing things.
Regards,
Jay
From: jdt-dev <jdt-dev-bounces@xxxxxxxxxxx>
On Behalf Of Mickael Istria
Sent: 16 March 2022 13:28
To: Eclipse JDT general developers list. <jdt-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: [jdt-dev] Foundation Code and Issue services reminder
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
|
This message came from outside your organization.
|
|
|
ZjQcmQRYFpfptBannerEnd
No, you are not alone here. I agree we should soon start working on the workflow document
to make it easier for the existing contributors. I expect/hope that the experts on GitHub help
us out with this.
Don't expect anyone to duplicate and maintain all that info into another location, just use existing reference doc.