docx4j source code on GitHub
Posted: Sat May 12, 2012 9:51 am
Git users:- I'm in the process of migrating the docx4j source code to GitHub. (In fact I'll do the 2.8.0 release from there.) The purpose of this topic is to solicit advice as to the details.
You can see the contents of svn trunk at https://github.com/plutext/docx4j
I used svn2git to make a git repository from svn. After running that, I have the following tags and branches in my local repo:
$ git tag -l
$ git branch -l
So far, all I've done is:
I could create a bunch of tags on GitHub, with:
In GitHub, these show up on the tags page as zip files you can download. Note that VERSION_2_7_1 and docx4j-2.7.1 are tags, not branches!
I could create the branches on GitHub, with:
This would create branches on GitHub for VERSION_2_7_0 etc.
I think I'd like the VERSION_2_7_1 tag to be on GitHub, and the VERSION_2_7_0 and possibly VERSION_2_6_0 branches. But what about the earlier ones - is there any point in adding these, bearing in mind that git clone creates remote-tracking branches for each branch in the cloned repository? (My intent is to eventually shut down the SVN repository, so if the earlier tags & branches are not pushed, this history would be lost)
Anything else to worry about at this point?
Thanks .. Jason
You can see the contents of svn trunk at https://github.com/plutext/docx4j
I used svn2git to make a git repository from svn. After running that, I have the following tags and branches in my local repo:
$ git tag -l
- Code: Select all
VERSION_2_0_0
VERSION_2_0_0@522
VERSION_2_1_0
VERSION_2_1_0@580
VERSION_2_2_1
VERSION_2_2_1@881
VERSION_2_2_2
VERSION_2_2_2@895
VERSION_2_7_0_RC
VERSION_2_7_0_RC@1576
VERSION_2_7_1
before-jaxb
before-jaxb@45
docx4j-2.7.1
lanl_20090114
lanl_20090114@620
$ git branch -l
- Code: Select all
VERSION_2_3_0
VERSION_2_3_0@1062
VERSION_2_4_0
VERSION_2_4_0@1145
VERSION_2_5_0
VERSION_2_5_0@1170
VERSION_2_6_0
VERSION_2_6_0@1326
VERSION_2_7_0
VERSION_2_7_0@1595
jaxb
jaxb@5
* master
So far, all I've done is:
- Code: Select all
git push -u origin master
I could create a bunch of tags on GitHub, with:
- Code: Select all
git push origin --tags
In GitHub, these show up on the tags page as zip files you can download. Note that VERSION_2_7_1 and docx4j-2.7.1 are tags, not branches!
I could create the branches on GitHub, with:
- Code: Select all
git push origin --all
This would create branches on GitHub for VERSION_2_7_0 etc.
I think I'd like the VERSION_2_7_1 tag to be on GitHub, and the VERSION_2_7_0 and possibly VERSION_2_6_0 branches. But what about the earlier ones - is there any point in adding these, bearing in mind that git clone creates remote-tracking branches for each branch in the cloned repository? (My intent is to eventually shut down the SVN repository, so if the earlier tags & branches are not pushed, this history would be lost)
Anything else to worry about at this point?
Thanks .. Jason