I see three valuable ways:
1. Only report issues into the separate system and let committers review these
items from time to time manually.
2. Report issues into the separate system and send daily reports to committers
or project lists that there are new incoming problems.
3. Report issues into
Hi Marcel,
thanks for the information.
>From the platform.ui side I'm not sure that we will be able to adapt "yet
another system" for looking at bug reports. IIRC the update of Bugzilla
worked fine for us, with the only issue that the duplicate bug dedection
has marking not the main bug and there
Same with CDT. In fact we have a lot of floating parts that we depend on and
depend on us, almost cyclical. It's only an issue when APIs change and we just
manage those cases carefully.
But with the size of they simrel, the offset model is out dated, especially if
the number is days.
Sent from
Hi
OCL is at +1 but depends on Xtext at +2.
We build at +1 against the latest Xtext I-build incurring a risk that we
might have to rebuild again at +2/+3. Hopefully such a rebuild would fix
only trivial problems.
We have been doing this for over a year and recall only one problem that
was s
I'm posting this to cross-projects because we are considering a change
that requires a significant dependency (jGit).
A new contribution to JSDT revolves around support for Bower javascript
package manager runtime, and this has a jGit dependency.
Our biggest issue from a build standpoint is we (W
