Thanks Konstantin. Even though you didn't list bugs as I requested ... 
I'll include in the "known contributing" group, if I have to freeze the 
rest. 

Thanks again, for your response, and contributing a quality project. 




From:   "Konstantin Komissarchik" <[email protected]>
To:     "'Cross project issues'" <[email protected]>, 
Date:   06/11/2015 01:51 PM
Subject:        Re: [cross-project-issues-dev] Rebuild process ... and 
question        for     sapphire
Sent by:        [email protected]



Sapphire is in the “would like to contribute a new build, but not critical 
to ask for a respin” category. RC4/Final includes a couple of minor fixes 
and documentation polish.I was caught up with family responsibilities and 
unable to contribute the build in time last night. It wouldn’t be the end 
of the world if simrel included our RC3, but there is no risk to anyone on 
the train from RC4 as fixes are safe and no one on the train is consuming 
Sapphire.
 
Thanks,
 
- Konstantin
 
 
From: [email protected] [
mailto:[email protected]] On Behalf Of David M 
Williams
Sent: Thursday, June 11, 2015 10:37 AM
To: [email protected]
Subject: [cross-project-issues-dev] Rebuild process ... and question for 
sapphire
 
Often, when doing a rebuild, as motivated by serious WindowBuilder 
problem, I would "freeze" all other content (to what is already in 
repository) except for the projects we specifically know are 
re-submitting. 

In this case, I am going to first try a normal re-build, and will just 
trust that no one else is "sneaking in changes" AND that everyone's repo 
is still "build-able". 

At the fist sign of trouble, though, I will go back to the "frozen 
content" method. Which brings me to my question for Sapphire. 

I noticed Sapphire changed URLs and qualifiers in b3aggrcon file. Is that 
only a move to final URL? Or were there some changes you want in the final 
version? I'm asking only to know if I should include Sapphire in "frozen" 
group (if needed) or in "known-rebuilding" group? (If the later, please 
document "what's changed" via bug numbers, etc., so everyone knows. 

Thanks, _______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to