[edit] WARNING: This is the _old_ Lustre wiki, and it is in the process of being retired. The information found here is all likely to be out of date. Please search the new wiki for more up to date information.

Git Transition Notice

From Obsolete Lustre Wiki
Jump to: navigation, search

(Updated: Dec 2009)

The Lustreā„¢ source repository is moving from CVS, where it has lived for the last 7+ years, to Git. This will simplify ongoing development of Lustre in a number of ways, including tracking of changes and history, improved merging of development branches into releases, and offline development.

Unfortunately, due to the lengthy use and abuse of CVS to manage the Lustre code, it is not possible to do a straight import of the entire CVS repository into Git using any existing tools. Rather than simply importing the current state of the code into Git and losing all of the history, we've worked to import the major development branches along with their full history into a single Git repository to maximize its usefulness.

When is this happening?

Monday, December 14, 2009, is the target date for switching all Lustre development from CVS to Git.

All CVS repositories will transition to read-only state on Friday, December 11, 2009 at 9:00 am CST. The CVS repository will remain in this read-only state for the duration of the conversion process. Please make your plans accordingly.

The conversion to Git will be done over the weekend (12/11/2009 - 12/13/2009). The resulting Git repository will be available on Monday, December 14, 2009, at 12:00 PM CST. The CVS tree will remain in a read-only state from this point on. All subsequent code changes must be done using Git.

Instructions on using Git with the Lustre code base can be found here:

What is supported?

The following branches are migrated to GIT:

b1_6
b1_8
b_release_1_6_7
b_release_1_8_0
b_release_1_8_1
master aka HEAD represents 2.0 work

A limited number of tags are also supported in the Git repository. Only v* tags post 1.6.7 are supported.

What is not supported?

The b1_4 branch will not be migrated and will be maintained under CVS.

Developer Migration Notes

To make your migration to Git easier, you should update any of your development CVS branches from the base, and land outstanding work in those development branches before Friday December 11, 2009. Working directories that contain uncommitted changes should also be updated, but can be done after the migration while the CVS repository is in a read-only mode.

Tags will be placed in the CVS repository to mark the point were the conversion was done:

B1_6_GIT_BASE
B1_8_GIT_BASE
B_RELEASE_1_6_7_GIT_BASE
B_RELEASE_1_8_0_GIT_BASE
B_RELEASE_1_8_1_GIT_BASE
B2_0_GIT_BASE

In addition tags will also be in place in the Git repository marking the spot of the conversion:

GIT_EPOCH_B1_6
GIT_EPOCH_B1_8
GIT_EPOCH_B_RELEASE_1_6_7
GIT_EPOCH_B_RELEASE_1_8_0
GIT_EPOCH_B_RELEASE_1_8_1
GIT_EPOCH_MASTER

Support

For support, send email to lustre-devel@sun.com.

Personal tools
Navigation