Re: [cross-project-issues-dev] Status and outlook for RC1 ... its going

[David M Williams <david_williams@xxxxxxxxxx>]

> There was no indication
that PTP was breaking the build. Where was the email to this list?

There's never automatic email to this
list ... just to those that the aggregator determines who is to "blame"
for problems. 
However, there are some problems that
are so bad, the EMF model can not be interpreted, so the aggregator does
not know whose email to send mail to.
These are easy for contributors to spot,
since there is the 'validate' function in the b3 aggregator, which I encourage
everyone to use before committing their contribution. 

I try to keep my eye on things, and
contact people personally in those types of situations ... but, I see that
as a convenience due to my friendly nature, so don't blame 
me if I didn't have time to watch your
build today at 4:30 to 8:00. All projects are responsible for making sure
the build works, notified or not.  

You can subscribe to Hudson's RSS feed
if you'd like to be notified of the status of every build, though, best
is not to rely on Hudson to tell you there is a problem, far better to
use the b3 aggregators "validate" function (which takes seconds)
and ideally the "validate aggregation" function, which admittedly
can can 10 or 15 minutes. 

Hope these tips help improve your process.






From:      
 Greg Watson <g.watson@xxxxxxxxxxxx>
To:      
 Cross project issues
<cross-project-issues-dev@xxxxxxxxxxx>, 
Date:      
 05/22/2013 09:53 PM
Subject:    
   Re: [cross-project-issues-dev]
Status and outlook for RC1 ...        its  
     going to be a late night!
Sent by:    
   cross-project-issues-dev-bounces@xxxxxxxxxxx

---

I was too busy trying to fix the problem so didn't open
the bug. It is 408769.

There was no indication that PTP was breaking the build.
Where was the email to this list?

 We have been waiting for an aggregation all day
so that we could test our package build.

Greg

On May 22, 2013, at 9:10 PM, David M Williams <david_williams@xxxxxxxxxx>
wrote:

From what I know so far, the answer
is "no". 

No bug number? No justification why everyone should be delayed to fix this
particular problem? Why it can not wait until RC2? 

Not to mention .... it was ptp that's been breaking the builds for some
time this afternoon, already holding up everyone, and I've already spent
an extra hour of my time fixing that and getting things just so they run
again. So, final question, why should I have confidence in a last minute
build submission? What extra processes have you put in place to verify
and validate your submission? 

Sincerely, 





From:        Greg
Watson <g.watson@xxxxxxxxxxxx>
To:        Cross
project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date:        05/22/2013
08:44 PM 
Subject:        Re:
[cross-project-issues-dev] Status and outlook for RC1 ... its    
   going to be a late night! 
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx

---

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_williams@xxxxxxxxxx>
wrote: 

Builds have been failing this afternoon, lots of contributions made. No
notices sent for failures. 
I finally took a look and discovered an "empty feature" in ptp.b3aggrecon
file: 

   <features> 
     <categories href="">
   </features> 

So, not sure if something was supposed to be there ... but, it's gone now.

I hope that will allow the aggregator to run to completion and if not,
at least perhaps provide an error message. 

I've discovered it gets very confused about empty features, probably especially
when naming a category. 

If things go smooth ... we might have our RC1 staging by 10 PM. If not
smooth ... then ... some time after that. 

Thanks, 
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev