Question regarding project contribution/branch management

7 views
Skip to first unread message

guillaume SEJOURNE

unread,
Jun 4, 2015, 3:30:01 AM6/4/15
to dita-...@googlegroups.com
Hi,

I'd like to get involved in the project, and though I pushed a few pull requests already, I have some questions regarding the way the
repository code is handled:

  • In general, what branch should I work to push a fix? master, develop, hotfix_n ?
  • What is the backport policy regarding these fixes, given they apply to multiple branches ?
    • push to master/develop,
    • the fixes are automatically backported/merged to the appropriate hotfix branch ?
  • I'm working exclusively on Linux, and I noticed all line-ending characters are CR/LF: if I submit pull requests, I suppose I need to convert my line-endings characters to CR/LF ?
  • How the release process handles updates?
    • I submitted a pull-request which was accepted on branch hotfix/2.0.2.
    • The current _bin package that's available for download on the DITA-OT website is the 2.0.1 tag.
    • How frequently is the stable branch updated ?
Also, is there some kind of continuous build / integration platform running tests against the various stable versions ?
I want to add a test that is quite specific to my projects, which installs the latest 2.0.x stable and installs my plugins automatically, and report new errors if any.
In the long run, I was thinking of making this a bit more generic and install custom extension plugins to run the same tests.
Is there any test framework you use / recommend I should look at ?

Thanks for the clarification.

-Guillaume
Reply all
Reply to author
Forward
0 new messages