Re: [ecf-dev] ECF move to runtime project

[Jeff McAffer <jeff@xxxxxxxxx>]

This is great news Scott.  The RT PMC looks forward to working with the 
ECF community.  Some comments on the info below.

- What is the "archive" area in CVS?  In general if you move something 
then you break old builds etc.  Elsewhere we have just left things where 
they were when they die off.

- You should talk about downloads somewhere. Note that the webmaster is 
going to a flat structure so your downloads will likely be at 
download.eclipse.org/ecf.  They need to know if you are doing a move or 
a copy of old content etc.  (I recommend copy again so that the 
transition does not break old builds and scripts)

- What are you doing about newsgroups?  You likely have the option to 
move to a flat name such as eclipse.ecf or some such.  Here you are not 
able to retain history etc.

- For bugs, that all just happens for free.  The mail addresses don't 
have the top level project in them and they seem to do the change at the 
database level so our experience in moving Equinox was that "things just 
work".

Jeff

Scott Lewis wrote:
> Hi ECFers,
>
> I've created a EF community bug here to track the ECF move from 
> Technology to runtime:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=246012
>
> On that bug is a mapping from current CVS projects to new projects 
> within the /cvsroot/rt/org.eclipse.ecf module:
>
> http://wiki.eclipse.org/ECF_Migration_to_Runtime_Project
>
> Please review this mapping for errors, omissions, incorrect 
> classifications, etc.
>
> The general story is that the top level modules (within 
> /cvsroot/rt/org.eclipse.ecf) are:
>
> applications
> archive
> doc
> examples
> framework
> incubation
> protocols
> providers
> releng
> server-side
> tests
>
> within these modules, all the modules previously named 'plugins' are 
> now named 'bundles'.   This organization is weakly patterned off of 
> the /cvsroot/rt/org.eclipse.equinox module structure.
>
> If you have any thoughts/comments about different organizations please 
> say so, and we'll discuss on this mailing list.  Nothing is etched in 
> stone at this point.
>
> Scott
>
>
>
>
>
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ecf-dev