Thanks criping. Comments below. From: dsdp-tcf-dev-bounces@xxxxxxxxxxx [mailto:dsdp-tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Ke, Liping
Sent: Wednesday, October 20, 2010 9:17 PM
To: DSDP TCF dev list; TCF Development; Zhang, Jessica
Subject: Re: [dsdp-tcf-dev] [tcf-dev] The Eclipse tools.cdt.tcfproject iscomplete! Hi Doug Our project(from Intel) which will be released within one month also depends on TCF current implementation. So the location change will affect us greatly. I think it’s impossible for us to change the code since release date is too close. [Doug] I think we can hold off for a month. I am troubled if you are just grabbing the TCF implementation off of trunk though. There is continuous development happening there. Ideally you should be using the 0.3 release that was made in June for Helios. In general, if we need to make more frequent releases, we can do that. We just need to know what the community wants and branch when appropriate. Unlike windriver tools, we’re open to all available eclipse resources. So if tcf is going with cdt for Helios right now, we might get into some trouble… [Doug] I’m not sure what you mean. These changes are to make TCF its own Eclipse project organizationally as a subproject of CDT, but still a separate entity when it comes to source code and releases. Also, I do know that Intel already adopts CDT for their Intel Compiler for Linux product. Thanks& Regards, criping From: dsdp-tcf-dev-bounces@xxxxxxxxxxx [mailto:dsdp-tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Schaefer, Doug
Sent: Wednesday, October 20, 2010 10:25 PM
To: TCF Development; DSDP TCF dev list
Subject: Re: [dsdp-tcf-dev] [tcf-dev] The Eclipse tools.cdt.tcf project iscomplete! Hi Michael, you are correct. This is why we need to co-ordinate downstream to see when it would be best for adopters to accept the changes. Since TCF is at version number < 1.0, we are free to make the changes per Eclipse guidance since 1.0 will mark a major version release. We can wait until the TCF release in June for Indigo. Or we can do an earlier release and change the names after that. I guess that brings up a question on when we should do our next release. Right now, I know of two adopters, Wind River and EDC in CDT. EDC is easy since it’s all in the open and doesn’t release again until Indigo. Wind River is tougher as we’re going through heavy product development right now. But I’d like to hear from others who would be impacted. Thanks, Doug From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Scharf, Michael
Sent: Tuesday, October 19, 2010 10:03 PM
To: DSDP TCF dev list; tcf-dev@xxxxxxxxxxx
Subject: Re: [tcf-dev] [dsdp-tcf-dev] The Eclipse tools.cdt.tcf project iscomplete! Hi Doug, I wonder what the impact of changing the package/plug-in
names is. It requires that all clients change their
code. Unfortunately, plugin and package names are not just
branding. They are part of the API. It is no problem as long
as all clients can change their source code. If we break the API anyway, maybe there are some
other breaking API changes that could be done in the same
'shot'. The question is: are there any pending changes that have not been
done so far, because they would break the API? Michael
From: dsdp-tcf-dev-bounces@xxxxxxxxxxx [mailto:dsdp-tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Sent: Tuesday, 19 October, 2010 17:02
To: DSDP TCF dev list
Subject: Re: [dsdp-tcf-dev] The Eclipse tools.cdt.tcf project is complete! BTW, subscribe to tcf-dev from the following link: https://dev.eclipse.org/mailman/listinfo/tcf-dev It's not listed in the directory yet. On Tue, Oct 19, 2010 at 10:58 AM, Doug Schaefer <cdtdoug@xxxxxxxxx> wrote: Hey gang, the new TCF project has been provisioned, we need to put together a plan to migrate our assets from DSDP to it's new homes. As you see listed below there are 6 things to consider. 1. SVN area. We will need to move the TCF SVN repo over to this new area. While doing that, we should also rename the Java packages in the plug-ins to remove the .tm since we are now known as org.eclipse.tcf. 2. Website. We just need to move the pages from the existing TM site over there. 3. Mailing list. We have a new mailing list, tcf-dev@xxxxxxxxxxx. Everyone should sign up for the new one and we should move discussions there. 4. Newsgroup. Not sure we need a newsgroup. Newsgroups are meant for user support but almost everyone involved in TCF comes from the dev side, at least for now. 5. Downloads. We could put nightly builds there, although we will most likely be integrating our build with the CDT build, at least for debug. 6. Bugzilla. We will need to move our bugs over to the new Project/Components. I have broken out I think 4 Components. We can always ask for more if we need them. Let me know when you feel it would be good to start the migration, especially the SVN repo which is most critical for those using TCF downstream. Any other feedback would be appreciated as well. Doug. ---------- Forwarded message ----------
From: Matthew Ward(Esq.) <matt.ward@xxxxxxxxxxx>
Date: Tue, Oct 19, 2010 at 10:48 AM
Subject: The Eclipse tools.cdt.tcf project is complete!
To: cdtdoug@xxxxxxxxx
Cc: Wayne Beaton <emo@xxxxxxxxxxx>, emo-records@xxxxxxxxxxx
Greetings,
The tools.cdt.tcf project is all set up and ready to go! Here are the
specifics (please communicate this information to your committers):
** Please note: If I was unable to locate committer records for some of the
initial committers they won't be able to access the resources below
until they receive their eclipse.org user id's.
1. SVN access:
Your initial committers have SVN access to dev.eclipse.org. They should
have received e-mails with their user id and password. Please use the
Committer Tools (https://dev.eclipse.org/committers/) to change your
password. To commit files to your repository, simply setup a new
repository location with the following information:
host: dev.eclipse.org
repository: /svnroot/tools/org.eclipse.tcf
method: svn+ssh
Feel free to create your subcomponents in this directory. I do not usually maintain
granular permissions to sub-components for projects, but if
you require specific access for only some committers, please let me know
what your needs are.
The above repository is also accessible, in an anonymous read-only
fashion, from http://dev.eclipse.org/svnroot/tools/org.eclipse.tcf
By default we do not enable committer access via https, if this is something you require please let us know.
2. Project Website
Your project website is up and ready to be authored. Simply set up a new
repository location:
host: dev.eclipse.org
repository: /cvsroot/org.eclipse
method: extssh
You have access to the www component, and specifically, the tcf/
directory. Anything you commit to the tcf/ directory will be
automatically published to http://www.eclipse.org/tcf/ within one
minute. We have set up a sample web page which can be viewed at http://www.eclipse.org/tcf
3. Mailing lists
The tcf-dev@xxxxxxxxxxx list has been created. You can subscribe to
the list here: https://dev.eclipse.org/mailman/listinfo/tcf-dev .
Subscription is required to post messages to the list.
Your mailing list will be added to the page(http://www.eclipse.org/mail/) after you have entered the required information into your ProjectInfo, via the Portal tools.
4. Newsgroups
Your newsgroup will be added to the page(http://www.eclipse.org/newsgroups/) after you have entered the required information into your ProjectInfo, via the Portal tools.:
If you need additional mailing lists or newsgroups, please contact
webmaster@xxxxxxxxxxx
5. Downloads
You have a downloads area with 2GB of space. To access this area, simply
use an SFTP or SCP client (such as CoreFTP or WinSCP) in SSH mode to
transfer your files. Refer to the File Paths section in the Committer
Tools for the downloads area to see where you should be publishing
downloadable files. Please be diligent when transferring
files: the downloads area is mirrored to over 70 mirror sites worldwide.
To link to a downloadable file, use the following path:
<a
href="" href="http://www.eclipse.org/downloads/download.php?file=/tcf/tcf-1.0.0.zip" target="_blank">http://www.eclipse.org/downloads/download.php?file=/tcf/tcf-1.0.0.zip">
This will ask users to pick a mirror site for the file, and it will add
RAP downloads to our download statistics (also in the Committer
Tools, Live Download Stats).
6. Bugzilla
Your bugzilla project, components, versions (if specified) and
milestones (of specified) have been created.
If your committers had a bugzilla account that matches the e-mail
address supplied to the Foundation, their account was granted standard
committer rights to edit and confirm bugs. If the committers didn't
have a bugzilla account, they should create one using the same e-mail
address as supplied to the Foundation and contact webmaster@xxxxxxxxxxx
to have their account upgraded with committer rights.
If you have any questions, or if you need assistance in using any of the
resources, please don't hesitate to drop me a line.
-Matt.
|
