RE: [cross-project-issues-dev] unified build process and current base bu

[David M Williams <david_williams@xxxxxxxxxx>]

Yes, and to emphasize ... I did not
mean to rule out this possibility ... just to encourage flexibility to
not force everyone to. 

But .. be careful what you wish for
Doug, you might end up having to do more "prep work"  for
the releng team than your current releng work. :)

Doug Schaefer <DSchaefer@xxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

04/28/2006 04:03 PM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

To	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc
Subject	RE: [cross-project-issues-dev] unified build process and current         base builder

In response to “it
would be better to have a good set of tools and processes that would fit
in to the way projects want to do builds and their processes, rather than
the reverse”, from the
CDT perspective, I don’t want to do builds at all J.
My not so hidden agenda is to get out of the releng business all together
and hand over the reins to a more central group with way more releng expertise
than we have on the CDT. I’m sure the CDT community would be happy to
follow any process this group would suggest.
 
Doug Schaefer, QNX Software
Systems
Eclipse CDT Project Lead, Tools
PMC member
http://cdtdoug.blogspot.com

---

From: cross-project-issues-dev-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of David
M Williams
Sent: Friday, April 28, 2006 3:42 PM
To: cross-project-issues-dev@xxxxxxxxxxx
Subject: [cross-project-issues-dev] unified build process and current
base builder
 

The topic of a unified build process is an interesting and worthwhile one
to pursue in the future. My own (quick) thoughts on it is that it would
be better to have a good set of tools and processes that would fit in to
the way projects want to do builds and their processes, rather than the
reverse ... some monolithic processes and extendable scripts that projects
would have to fit them selves in to. And,  I suggest, most of these
tools and/or scripts should become like other Eclipse deliverables .. API
level of stability and support, "owned" by a responsible project,
etc., 


Which reminds me ... I know I sure enjoy using the "basebuilder"
from the Eclipse Project (we owe them a debt of gratitude ... or chocolate
:) 

 ... but there is  one timing issue we should plan for: when (or ..
should I say if ? )  there is a "final" basebuilder for
the Callisto release, when will that be available,   Do other projects
use it? (does anyone not use it :)  I'd just like to be sure we use
"the right" one as we near the end ... so, thought I'd ask now
if "we" (i.e. Kim and Sonia :) 
should offer a proposed plan for availability? 

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