docx4j source code on GitHub

[jason]

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

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

[Nanocom]

If you are not maintaining versions < 2.6, I think losing the history of the related branches won't be a big problem.
Regarding the tags, you obviously don't need to push them all since a tag is equivalent to naming a commit.
So if I were you, I would push 2.6 and 2.7 branches, master for 2.8, and tags for versions > 2.6.
Anyway, very nice idea to migrate on GitHub

[jason]

Thanks for your thoughts.

I've ended up creating https://github.com/plutext/docx4j/branches for each of the 2.x versions, since it seems a pity to lose the history when it is so easy to keep.

One thing which looks a bit weird to me though .. in for example https://github.com/plutext/docx4j/tree/VERSION_2_7_0 there is this entry:

Code: Select all

wagon-svn-pom.xml   6 days ago   Remove intermediate docx4j dir


Well, I "Remove intermediate docx4j dir" on master only.

If you click into the history https://github.com/plutext/docx4j/commi ... vn-pom.xml it correctly says it was last modified 4 years ago.

Is this a bug in the github user interface, or is this how it communicates the date that that file was last modified, on some branch? If the latter, you'd think github would try to distinguish between a modification on this branch, and a modification on some other branch (maybe by giving both dates).