Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Final 2.1.1 release?

Chris, for the 2.1.1 builds you need to:

- create the R2_1_maintenance branch for the fragment if it doesn't exist
already (use R2_1 as the root)
- check out the R2_1_maintenance branch into your workspace
- make the changes in your workspace
- release your changes to the repository
- check out the file in the R2_1_maintenance branch
- tag your fragment as a version in the repository (we have been using the
convention r21x_20030603)
- update the version in the file with the new version
- release the map file to the repository

Note that the last 3 can be taken care of at once by using the "Release..."
action available from the RelEng release tool on the RelEng team page.

I've checked and you do have permissions to write to the project in the
repository. Try the above steps and let me know if you still can't release
your code and I will investigate further.


Monday, June 02, 2003 6:25 PM
To: eclipse-dev@xxxxxxxxxxx
From: Chris McKillop <cdm@xxxxxxx>
Subject: Re: [eclipse-dev] Final 2.1.1 release?

On Mon, Jun 02, 2003 at 01:05:29PM -0400, Jim des Rivieres wrote:
> > Are there any plans for a final release of 2.1.1 in the near future?
> We're testing a new 2.1.1 build today. We should have a final 2.1.1
> release in the can by the end of this week, or next week at the outside.

I am trying to get the with the correct version information
to pull in the fixed core.resources.qnx fragment into the 2.1.1 builds.  At
first I though I would just move the Root_R2_1_maintenance tag to the HEAD
and I would be done.  Doesn't appear to want to let me.  So then I tried
checking out Root_R2_1_maintenance and commiting a change to that
Branch.  That didn't work either!!

So, how do I tag/branch/merge the mapfile to get it into the 2.1.1 builds?


Chris McKillop <cdm@xxxxxxx>   "The faster I go, the behinder I get."
Software Engineer, QSSL                   -- Lewis Carroll --

eclipse-dev mailing list

Back to the top