Fw: [equinox-dev] Code move timeline
Unfortunately due to some IP legal issues that need to be worked out (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=242307) we are not ready to perform the move this week. Given that M1 week is next week we will have to delay the move until mid August. Stay tuned. Tom - Forwarded by Thomas Watson/Austin/IBM on 07/30/2008 04:22 PM - From: Thomas Watson/Austin/IBM To: Equinox development mailing list equinox-dev@eclipse.org Date: 07/28/2008 04:51 PM Subject:Re: [equinox-dev] Code move timeline I opened a bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=242307 to initiate the CVS move/copy. I documented the projects that are moving and their new location in the RT CVS repository at http://wiki.eclipse.org/Equinox_Eclipse_to_RT_Migration#CVS_Projects. Please let me know if you find any errors. I requested that they give us a heads on the time they will perform the move so that we have some warning before the move actually occurs. Stay tuned. Tom From:! Jeff McAffer [EMAIL PROTECTED] To: Equinox development mailing list equinox-dev@eclipse.org Date: 07/25/2008 03:20 AM Subject:Re: [equinox-dev] Code move timeline Would be good to summarize the transformation/copy information in a new list somewhere. We will have to give this to the webmaster to execute the copy operation anyway and there seem to have been some tweaks since the original proposal. Jeff Thomas Watson wrote: There will still be a bundles directory. Basically the proposal at http://wiki.eclipse.org/Equinox_CVS_Structure will be used. Tom Inactive hide details for DJ Houghton ---07/22/2008 02:05:23 PM---As discussed in the Equinox call today, I compared the contenDJ Houghton ---07/22/2008 02:05:23 PM---As discussed in the Equinox call today, I compared the contents of the p2 project set files with the From:DJ Houghton [EMAIL PROTECTED] To: Equinox development mailing list equinox-dev@eclipse.org Date:07/22/2008 02:05 PM Subject: Re: [equinox-dev] Code move timeline As discussed in the Equinox call today, I compared the contents of the p2 project set files with the list of bundles in the repository at: org.eclipse.equinox/p2/bundles/ and they are the same... all bundle should be copied during the Equinox move. (bundles which are not listed in the current psf file are part of the new publisher work) As well, we should copy the p2 releng project: org.eclipse.equinox/p2/org.eclipse.equinox.p2.releng Although I am not sure the best location for it. Will the resulting folders in the RT repository have bundle/ folders with the bundles in them, or will the bundles be at the root? (e.g. org.eclipse.equinox/p2 or org.eclipse.equinox/p2/bundles?) Inactive hide details for Thomas Watson [EMAIL PROTECTED]Thomas Watson [EMAIL PROTECTED] Thomas Watson [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED
Re: [equinox-dev] Code move timeline
I opened a bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=242307 to initiate the CVS move/copy. I documented the projects that are moving and their new location in the RT CVS repository at http://wiki.eclipse.org/Equinox_Eclipse_to_RT_Migration#CVS_Projects. Please let me know if you find any errors. I requested that they give us a heads on the time they will perform the move so that we have some warning before the move actually occurs. Stay tuned. Tom From: Jeff McAffer [EMAIL PROTECTED] To: Equinox development mailing list equinox-dev@eclipse.org Date: 07/25/2008 03:20 AM Subject:Re: [equinox-dev] Code move timeline Would be good to summarize the transformation/copy information in a new list somewhere. We will have to give this to the webmaster to execute the copy operation anyway and there seem to have been some tweaks since the original proposal. Jeff Thomas Watson wrote: There will still be a bundles directory. Basically the proposal at http://wiki.eclipse.org/Equinox_CVS_Structure will be used. Tom Inactive hide details for DJ Houghton ---07/22/2008 02:05:23 PM---As discussed in the Equinox call today, I compared the contenDJ Houghton ---07/22/2008 02:05:23 PM---As discussed in the Equinox call today, I compared the contents of the p2 project set files with the From:DJ Houghton [EMAIL PROTECTED] To: Equinox development mailing list equinox-dev@eclipse.org Date:07/22/2008 02:05 PM Subject: Re: [equinox-dev] Code move timeline As discussed in the Equinox call today, I compared the contents of the p2 project set files with the list of bundles in the repository at: org.eclipse.equinox/p2/bundles/ and they are the same... all bundle should be copied during the Equinox move. (bundles which are not listed in the current psf file are part of the new publisher work) As well, we should copy the p2 releng project: org.eclipse.equinox/p2/org.eclipse.equinox.p2.releng Although I am not sure the best location for it. Will the resulting folders in the RT repository have bundle/ folders with the bundles in them, or will the bundles be at the root? (e.g. org.eclipse.equinox/p2 or org.eclipse.equinox/p2/bundles?) Inactive hide details for Thomas Watson [EMAIL PROTECTED]Thomas Watson [EMAIL PROTECTED] Thomas Watson [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] To 07/17/2008 02:04 PM Equinox development mailing list [EMAIL PROTECTED] pse.org Please respond to Equinox development mailing list cc equinox-dev@eclipse.org Subject Re: [equinox-dev
Re: [equinox-dev] Code move timeline
into From: Pascal Rapicault [EMAIL PROTECTED] To: Equinox development mailing list equinox-dev@eclipse.org Date: 07/15/2008 10:18 AM Subject:[equinox-dev] Code move timeline Hi, I would like to know what is the time line for moving the equinox code into the runtime repository? PaScaL___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev inline: graycol.gifinline: pic12833.gifinline: ecblank.gifinline: 0B709122.gifinline: 0B184471.gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Code move timeline
Looks very good, totally agree on Bundles being better as separate categories. It seems that several Equinox bundles are not in the list: org.eclipse.equinox.executable org.eclipse.equinox.launcher org.eclipse.equinox.servlet.api org.eclipse.equinox.startup org.eclipse.equinox.supplement org.eclipse.osgi org.eclipse.osgi.tests (a couple of those bundles probably aren't relevant anymore). In terms of placing bundles into categories, the org.eclipse.equinox.preferences seems to be out of place in the osgi-compendum. Maybe, place it in the components? One other point, depending on overhead involved, it might be worth having launcher as a separate category. Today framework = OSGi + launcher, and those two items are different in just about every dimension. Then in CVS structure below instead of org.eclipse.equinox/framework there would be org.eclipse.equinox/launcher and all OSGi-related items would go into org.eclipse.equinox/osgi-compendium. Thanks, Oleg Thomas Watson [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 07/17/2008 02:04 PM Please respond to Equinox development mailing list equinox-dev@eclipse.org To Equinox development mailing list equinox-dev@eclipse.org cc Subject Re: [equinox-dev] Code move timeline We discussed this at the Tuesday Equinox call. It looks like a large part of the team will be on vacation at the end of July. The proposal is to move the equinox projects to RT during the week of July 28th. We also discussed what to do with the equinox incubator. At this time we are going to wait for the new Eclipse Development Process to be approved (hopefully in August). The new process should allow us to create incubator projects under any project in Eclipse. This will allow us to create an incubator project for equinox directly under the equinox project in RT. Jeff and I have been discussing the layout of the different components of Equinox. Today we have Bundles, Framework, p2, Security. The Bundles category has become kind of a dumping ground for many unrelated bundles. We would like to split these bundles out into three categories: osgi-compendium - All bundles that implement one of the osgi compendium specifications. This includes the following projects: org.eclipse.equinox.app org.eclipse.equinox.cm org.eclipse.equinox.device org.eclipse.equinox.ds org.eclipse.equinox.event org.eclipse.equinox.http org.eclipse.equinox.http.jetty (jetty5 and jetty6 impls) org.eclipse.equinox.io org.eclipse.equinox.ip org.eclipse.equinox.log org.eclipse.equinox.metatype org.eclipse.equinox.preferences org.eclipse.equinox.useradmin org.eclipse.equinox.util org.eclipse.equinox.wireadmin org.eclipse.osgi.services org.eclipse.osgi.util components - The bundles that provide infrastructure to developing components in Equinox. This includes the following projects: org.eclipse.equinox.common org.eclipse.equinox.registry org.eclipse.equinox.transforms.hook org.eclipse.equinox.transforms.xslt server-side - The server side bundles. org.eclipse.equinox.http.registry org.eclipse.equinox.http.servlet org.eclipse.equinox.http.servletbridge org.eclipse.equinox.jsp.jasper org.eclipse.equinox.jsp.jasper.registry org.eclipse.equinox.servletbridge This would result in the following CVS structure in RT org.eclipse.equinox/components org.eclipse.equinox/framework org.eclipse.equinox/osgi-compendium org.eclipse.equinox/p2 org.eclipse.equinox/security org.eclipse.equinox/server-side All commiters with rights to the projects contained in Bundles will continue to have access to all the projects which got moved to the three new categories. We are not trying to create more fine grained commit rights. Instead we are just trying to create a layout that makes sense in CVS and Bugzilla. Thoughts? Tom Pascal Rapicault ---07/15/2008 10:18:13 AM---Hi, I would like to know what is the time line for moving the equinox code into From: Pascal Rapicault [EMAIL PROTECTED] To: Equinox development mailing list equinox-dev@eclipse.org Date: 07/15/2008 10:18 AM Subject: [equinox-dev] Code move timeline Hi, I would like to know what is the time line for moving the equinox code into the runtime repository? PaScaL___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev image/gifimage/gifimage/gifimage/gifimage/gifimage/gifimage/gifimage/gifimage/gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Code move timeline
yes, Equinox is moving and all future releases should come from the
"new" repo in RT-land.
Jeff
Thomas Watson wrote:
Yes we will retain history. We do not plan to physically remove
the old tags and branches from the /cvsroot/eclipse repo so the old map
files should continue to be able to build the maintenance builds. I
think we will remove all the content from HEAD and place a readme in
each project stating where the project has moved. But this does not
imply that the old tags and branches will be deleted.
But this does raise the question about which repository should be used
for 3.4.x. Which repo should we use to develop 3.4.x? My vote is to do
all future releases out of the Runtime repo, including point releases
(3.4.1). In this case the 3.4.x map files should only have to be
updated with the new location when the first fix is dropped into the
new Runtime repo.
Tom
Kim Moir
---07/17/2008 04:06:46 PM---So I assume that the cvs history will be
retained when the bundles are moved to the RT project's re
From:
Kim Moir [EMAIL PROTECTED]
To:
Equinox development mailing list
equinox-dev@eclipse.org
Date:
07/17/2008 04:06 PM
Subject:
Re: [equinox-dev] Code move timeline
So I assume that the cvs history will be retained when the bundles are
moved to the RT project's repository? The 3.4.x map files will need to
be updated with the new location too so we don't have build breakage
Kim
Thomas Watson
[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
07/17/2008 02:04 PM
Please respond to
Equinox development mailing list equinox-dev@eclipse.org
To
Equinox development
mailing list equinox-dev@eclipse.org
cc
Subject
Re: [equinox-dev] Code
move timeline
We discussed this at the Tuesday Equinox call. It looks like a large
part of the team will be on vacation at the end of July. The proposal
is to move the equinox projects to RT during the week of July 28th.
We also discussed what to do with the equinox incubator. At this time
we are going to wait for the new Eclipse Development Process to be
approved (hopefully in August). The new process should allow us to
create incubator projects under any project in Eclipse. This will allow
us to create an incubator project for equinox directly under the
equinox project in RT.
Jeff and I have been discussing the layout of the different components
of Equinox. Today we have Bundles, Framework, p2, Security. The Bundles
category has become kind of a dumping ground for many unrelated
bundles. We would like to split these bundles out into three
categories:
osgi-compendium - All bundles that implement one of the osgi compendium
specifications. This includes the following projects:
org.eclipse.equinox.app
org.eclipse.equinox.cm
org.eclipse.equinox.device
org.eclipse.equinox.ds
org.eclipse.equinox.event
org.eclipse.equinox.http
org.eclipse.equinox.http.jetty (jetty5 and jetty6 impls)
org.eclipse.equinox.io
org.eclipse.equinox.ip
org.eclipse.equinox.log
org.eclipse.equinox.metatype
org.eclipse.equinox.preferences
org.eclipse.equinox.useradmin
org.eclipse.equinox.util
org.eclipse.equinox.wireadmin
org.eclipse.osgi.services
org.eclipse.osgi.util
components - The bundles that provide infrastructure to developing
components in Equinox. This includes the following projects:
org.eclipse.equinox.common
org.eclipse.equinox.registry
org.eclipse.equinox.transforms.hook
org.eclipse.equinox.transforms.xslt
server-side - The server side bundles.
org.eclipse.equinox.http.registry
org.eclipse.equinox.http.servlet
org.eclipse.equinox.http.servletbridge
org.eclipse.equinox.jsp.jasper
org.eclipse.equinox.jsp.jasper.registry
org.eclipse.equinox.servletbridge
This would result in the following CVS structure in RT
org.eclipse.equinox/components
org.eclipse.equinox/framework
org.eclipse.equinox/osgi-compendium
org.eclipse.equinox/p2
org.eclipse.equinox/security
org.eclipse.equinox/server-side
All commiters with rights to the projects contained in Bundles will
continue to have access to all the projects which got moved to the
three new categories. We are not trying to create more fine grained
commit rights.
Re: [equinox-dev] Code move timeline
I like this and agree that bundles had unfortunately become a dumping ground. The separation you guys have done looks good to me. One nit... I think we probably want org.eclipse.equinox.http.servlet in the osgi-compendium as it's what really provides the Http Service implementation and also is a dependency of org.eclipse.equinox.http.jetty. -Simon | | From: | | --| |Thomas Watson [EMAIL PROTECTED] | --| | | To:| | --| |Equinox development mailing list equinox-dev@eclipse.org | --| | | Date: | | --| |07/17/2008 02:05 PM | --| | | Subject: | | --| |Re: [equinox-dev] Code move timeline | --| We discussed this at the Tuesday Equinox call. It looks like a large part of the team will be on vacation at the end of July. The proposal is to move the equinox projects to RT during the week of July 28th. We also discussed what to do with the equinox incubator. At this time we are going to wait for the new Eclipse Development Process to be approved (hopefully in August). The new process should allow us to create incubator projects under any project in Eclipse. This will allow us to create an incubator project for equinox directly under the equinox project in RT. Jeff and I have been discussing the layout of the different components of Equinox. Today we have Bundles, Framework, p2, Security. The Bundles category has become kind of a dumping ground for many unrelated bundles. We would like to split these bundles out into three categories: osgi-compendium - All bundles that implement one of the osgi compendium specifications. This includes the following projects: org.eclipse.equinox.app org.eclipse.equinox.cm org.eclipse.equinox.device org.eclipse.equinox.ds org.eclipse.equinox.event org.eclipse.equinox.http org.eclipse.equinox.http.jetty (jetty5 and jetty6 impls) org.eclipse.equinox.io org.eclipse.equinox.ip org.eclipse.equinox.log org.eclipse.equinox.metatype org.eclipse.equinox.preferences org.eclipse.equinox.useradmin org.eclipse.equinox.util org.eclipse.equinox.wireadmin org.eclipse.osgi.services org.eclipse.osgi.util components - The bundles that provide infrastructure to developing components in Equinox. This includes the following projects: org.eclipse.equinox.common org.eclipse.equinox.registry org.eclipse.equinox.transforms.hook org.eclipse.equinox.transforms.xslt server-side - The server side bundles. org.eclipse.equinox.http.registry org.eclipse.equinox.http.servlet org.eclipse.equinox.http.servletbridge org.eclipse.equinox.jsp.jasper org.eclipse.equinox.jsp.jasper.registry org.eclipse.equinox.servletbridge This would result in the following CVS structure in RT org.eclipse.equinox/components org.eclipse.equinox/framework org.eclipse.equinox/osgi-compendium org.eclipse.equinox/p2 org.eclipse.equinox/security org.eclipse.equinox/server-side All commiters with rights to the projects contained in Bundles will continue to have access to all the projects which got moved to the three new categories. We are not trying to create more fine grained commit rights. Instead we are just trying to create a layout that makes sense in CVS and Bugzilla. Thoughts? Tom Inactive hide details for Pascal Rapicault ---07/15/2008 10:18:13 AM---Hi, I would like to know what is the time line for movinPascal
Re: [equinox-dev] Code move timeline
Thanks Simon. Yes org.eclipse.equinox.http.servlet belongs in osgi-compendium. Tom From: Simon Kaegi [EMAIL PROTECTED] To: Equinox development mailing list equinox-dev@eclipse.org Date: 07/17/2008 03:14 PM Subject:Re: [equinox-dev] Code move timeline I like this and agree that bundles had unfortunately become a dumping ground. The separation you guys have done looks good to me. One nit... I think we probably want org.eclipse.equinox.http.servlet in the osgi-compendium as it's what really provides the Http Service implementation and also is a dependency of org.eclipse.equinox.http.jetty. -Simon Inactive hide details for Thomas Watson ---07/17/2008 02:05:59 PM---We discussed this at the Tuesday Equinox call. It looks likThomas Watson ---07/17/2008 02:05:59 PM---We discussed this at the Tuesday Equinox call. It looks like a large part of the team will be on vacation at the end of July. T. From:Thomas Watson [EMAIL PROTECTED] To: Equinox development mailing list equinox-dev@eclipse.org Date:07/17/2008 02:05 PM Subject: Re: [equinox-dev] Code move timeline We discussed this at the Tuesday Equinox call. It looks like a large part of the team will be on vacation at the end of July. The proposal is to move the equinox projects to RT during the week of July 28th. We also discussed what to do with the equinox incubator. At this time we are going to wait for the new Eclipse Development Process to be approved (hopefully in August). The new process should allow us to create incubator projects under any project in Eclipse. This will allow us to create an incubator project for equinox directly under the equinox project in RT. Jeff and I have been discussing the layout of the different components of Equinox. Today we have Bundles, Framework, p2, Security. The Bundles category has become kind of a dumping ground for many unrelated bundles. We would like to split these bundles out into three categories: osgi-compendium - All bundles that implement one of the osgi compendium specifications. This includes the following projects: org.eclipse.equinox.app org.eclipse.equinox.cm org.eclipse.equinox.device org.eclipse.equinox.ds org.eclipse.equinox.event org.eclipse.equinox.http org.eclipse.equinox.http.jetty (jetty5 and jetty6 impls) org.eclipse.equinox.io org.eclipse.equinox.ip org.eclipse.equinox.log org.eclipse.equinox.metatype org.eclipse.equinox.preferences org.eclipse.equinox.useradmin org.eclipse.equinox.util org.eclipse.equinox.wireadmin org.eclipse.osgi.services org.eclipse.osgi.util components - The bundles that provide infrastructure to developing components in Equinox. This includes the following projects: org.eclipse.equinox.common org.eclipse.equinox.registry org.eclipse.equinox.transforms.hook org.eclipse.equinox.transforms.xslt server-side - The server side bundles. org.eclipse.equinox.http.registry org.eclipse.equinox.http.servlet org.eclipse.equinox.http.servletbridge org.eclipse.equinox.jsp.jasper org.eclipse.equinox.jsp.jasper.registry org.eclipse.equinox.servletbridge This would result in the following CVS structure in RT org.eclipse.equinox/components org.eclipse.equinox/framework org.eclipse.equinox/osgi-compendium org.eclipse.equinox/p2 org.eclipse.equinox/security org.eclipse.equinox/server-side All commiters with rights to the projects contained in Bundles will continue to have access to all the projects which got moved to the three new categories. We are not trying to create more fine grained commit rights. Instead we are just trying to create a layout that makes sense in CVS and Bugzilla. Thoughts? Tom Inactive hide details for Pascal Rapicault ---07/15/2008 10:18:13 AM---Hi, I would like
Re: [equinox-dev] Code move timeline
So I assume that the cvs history will be retained when the bundles are moved to the RT project's repository? The 3.4.x map files will need to be updated with the new location too so we don't have build breakage Kim Thomas Watson [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 07/17/2008 02:04 PM Please respond to Equinox development mailing list equinox-dev@eclipse.org To Equinox development mailing list equinox-dev@eclipse.org cc Subject Re: [equinox-dev] Code move timeline We discussed this at the Tuesday Equinox call. It looks like a large part of the team will be on vacation at the end of July. The proposal is to move the equinox projects to RT during the week of July 28th. We also discussed what to do with the equinox incubator. At this time we are going to wait for the new Eclipse Development Process to be approved (hopefully in August). The new process should allow us to create incubator projects under any project in Eclipse. This will allow us to create an incubator project for equinox directly under the equinox project in RT. Jeff and I have been discussing the layout of the different components of Equinox. Today we have Bundles, Framework, p2, Security. The Bundles category has become kind of a dumping ground for many unrelated bundles. We would like to split these bundles out into three categories: osgi-compendium - All bundles that implement one of the osgi compendium specifications. This includes the following projects: org.eclipse.equinox.app org.eclipse.equinox.cm org.eclipse.equinox.device org.eclipse.equinox.ds org.eclipse.equinox.event org.eclipse.equinox.http org.eclipse.equinox.http.jetty (jetty5 and jetty6 impls) org.eclipse.equinox.io org.eclipse.equinox.ip org.eclipse.equinox.log org.eclipse.equinox.metatype org.eclipse.equinox.preferences org.eclipse.equinox.useradmin org.eclipse.equinox.util org.eclipse.equinox.wireadmin org.eclipse.osgi.services org.eclipse.osgi.util components - The bundles that provide infrastructure to developing components in Equinox. This includes the following projects: org.eclipse.equinox.common org.eclipse.equinox.registry org.eclipse.equinox.transforms.hook org.eclipse.equinox.transforms.xslt server-side - The server side bundles. org.eclipse.equinox.http.registry org.eclipse.equinox.http.servlet org.eclipse.equinox.http.servletbridge org.eclipse.equinox.jsp.jasper org.eclipse.equinox.jsp.jasper.registry org.eclipse.equinox.servletbridge This would result in the following CVS structure in RT org.eclipse.equinox/components org.eclipse.equinox/framework org.eclipse.equinox/osgi-compendium org.eclipse.equinox/p2 org.eclipse.equinox/security org.eclipse.equinox/server-side All commiters with rights to the projects contained in Bundles will continue to have access to all the projects which got moved to the three new categories. We are not trying to create more fine grained commit rights. Instead we are just trying to create a layout that makes sense in CVS and Bugzilla. Thoughts? Tom Pascal Rapicault ---07/15/2008 10:18:13 AM---Hi, I would like to know what is the time line for moving the equinox code into From: Pascal Rapicault [EMAIL PROTECTED] To: Equinox development mailing list equinox-dev@eclipse.org Date: 07/15/2008 10:18 AM Subject: [equinox-dev] Code move timeline Hi, I would like to know what is the time line for moving the equinox code into the runtime repository? PaScaL___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev image/gifimage/gifimage/gifimage/gifimage/gifimage/gifimage/gifimage/gifimage/gif___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
