“The Committers of a Project or component decide which changes may be committed
to the master code base of a Project or component respectively. Three +1 ('yes'
votes) with no -1 ('no' votes or vetoes) are needed to approve a code change.
Vetoes must be followed by an explanation for the veto wit
Attention: The JobManager implementation was changed!
The old JobMangager implementation notified IJobChangeListener about various
IJobChangeEvent without strict order in various threads. For example
scheduled() was called in a thread that did call schedule() on a job while
done() was normally cal
cucumber is also honest about what to expect from a bug:
"Please bear in mind that this project is almost entirely developed by
volunteers. If you do not provide the implementation yourself (or pay someone
to do it for you), the bug might never get fixed. If it is a serious bug, other
people tha
Well, if direct pushing to the repository is disallowed it should be disabled.
I accidently made my first error with not creating a PR. And got nor error
message. Highly confusing.
If possible the error message should provide a link to a how-to-contribute.
Jörg
_
+1 stop
-Ursprüngliche Nachricht-
Von: platform-dev Im Auftrag von Andrey
Loskutov
Gesendet: Donnerstag, 17. Februar 2022 09:59
An: platform-dev
Betreff: [platform-dev] Vote to stop bug auto-closing in all Eclipse platform
projects
Hi all,
this is a follow up on PMC response
https:/
I dislike stupid robots judging human contributions which come from heart. I
also dislike triage. As long as a bug is not planned with target Milestone and
(voluntary) assignee it won’t be done anyways. But still it is a valid report
that later might gain attention.
