Please note, that every PR on master with trivial doc change will trigger JDT Jenkins build, and that will load Jenkins for 1/2 hour at least.
This is not needed but will disturb others (assuming others are active at same time) because Jenkins instances aren't unlimited.
Also it will spam main repo git log (there are people trying to use it time to time to track regressions etc).
What is wrong with github default wiki?
Kind regards,
Andrey Loskutov
Спасение утопающих - дело рук самих утопающих
https://www.eclipse.org/user/aloskutov
Gesendet: Dienstag, 10. Mai 2022 um 10:07 Uhr
Von: "Thomas Mäder" <tmader@xxxxxxxxxx>
An: "Mickael Istria" <mistria@xxxxxxxxxx>, "Eclipse JDT general developers list." <jdt-dev@xxxxxxxxxxx>
Betreff: Re: [jdt-dev] Wikis on jdt Repos?
------ Original Message ------
From: "Mickael Istria" <mistria@xxxxxxxxxx>
To: "Thomas Mäder" <tmader@xxxxxxxxxx>; "Eclipse JDT general developers list." <jdt-dev@xxxxxxxxxxx>
Sent: 10/05/2022 09:30:56
Subject: Re: [jdt-dev] Wikis on jdt Repos?
On Tue, May 10, 2022 at 9:25 AM Thomas Mäder <tmader@xxxxxxxxxx> wrote:
I was wondering where we should put internal process documentation like how to do triaging.
What about having them in the repo together with the code, in a dedicated "development-doc" or "contributing" folder or something like that? It gives the benefit that it's easier to keep things sync'd with the actual payload, is easier to track contributions to the doc/process just like contribution to the code, and prevent from multiplying the entry points.
This is what we do on all other Eclipse projects I'm working on, and so far no concern was raised.
That's the alternative, basically. Have a "docs" or "process" folder?
/Thomas
_______________________________________________ jdt-dev mailing list jdt-dev@xxxxxxxxxxx To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jdt-dev
