RE: [cdt-dev] Idea on cvs project creation

[Sebastien Marineau <sebastien@xxxxxxx>]

That's what other projects have done and I think it would make it a lot
easier and flexible.

There are a few drawbacks like disruption of currently checked-out src, but
that
is something we can manage given that we can probably reach the majority
of affected folks through the NG and mailing list.

If we want to do this, we should decide quickly -- Mike (Eclipse webmaster)
is still
working on the commiter changes we submitted a while back, but is nearly
done 
phase 1 (e.g. the commiter/project rationalization but not the bugzilla
changes). We can
probably still switch to your scheme before he commits his changes, but he
may not
be too happy about it... better now than later though.

Sebastien


> -----Original Message-----
> From: Douglas Schaefer [mailto:dschaefe@xxxxxxxxxx]
> Sent: Monday, April 19, 2004 1:30 PM
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] Idea on cvs project creation
> 
> 
> Hey gang,
> 
> It seems our cvs project creation requests seem to flow into 
> the ether or 
> at best, take forever to get implemented. Here's a thought I 
> had after 
> talking with one of the Eclipse PDE people. One thing we could do is 
> create CVS projects for each of the committer groups: e.g. cdt-core, 
> cdt-debug, etc. and then put our plugin projects under them. 
> This would 
> then allow committers to create new plugins or features by 
> themselves. 
> Aside from the disruption of current checkouts, is there anything 
> fundamentally wrong with this approach? Thoughts/opinions? Anyone?
> 
> Doug Schaefer, IBM's Eclipse CDT Architect
> Ottawa (Palladium), Ontario, Canada
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
>