On May 22, 2013, at 11:43 PM, David M Williams david_willi...@us.ibm.com
wrote:
There's no change in policy. Projects choose to be in the (our) common repo.
Part of that is to provide valid input to the build. Normally the tools work
well to send out notifications for problems.
Hi Greg,
[1] shows that the build was triggered by only one SCM change with the comment:
For ptp, add org.eclipse.ptp.debug.sdm feature. Before of this change the
build was working. So IMO it suggests itself that this commit was breaking the
build.
BTW: This is exactly the way how I was
Hi,
maybe I can step up here, since comments from me :-) are already in this
thread. I have to admit that Riena had problems with the aggregation too in the
past.
I also thought for a long time (actually years) that the only way to try a
new contribution is to build, sign, upload, change
David,
BTW, I do appreciate all the work you do to ensure the releases are successful.
It can be a bit frustrating when things don't go quite right, so we need to all
work together to ensure that everything goes as smoothly as possible.
Cheers,
Greg
On May 23, 2013, at 7:38 AM, Greg Watson
David,
We have a breaking issue that was just fixed, and our build is currently
running. I'd like to request a respin at 10pm if possible.
Thanks,
Greg
On May 22, 2013, at 8:00 PM, David M Williams david_willi...@us.ibm.com wrote:
Builds have been failing this afternoon, lots of
David,
Somewhat late at night to be arguing, but I find this statement perplexing:
All projects are responsible for making sure the build works, notified or
not.
I have no idea how the aggregation works, nor have I seen any policy that
indicates that I need to. I'm happy to take
