Community Support for OpenDocMan (Deprecated)

Full Version: Development and release engineering process
You're currently viewing a stripped down version of our content. View the full version with proper formatting.


Hi Stephen, congratulations and thank you for I'm installing it now for testing.

Could you clarify the development repo situation? A post Apr 26 to the Announcements sub-forum says development is now hosted on Github, while an announcement on the OpenDocMan website also Apr 26 says the code VCS is now Git but still hosted on SourceForge, and the Develop page on the SourceForge project site still refers to the SourceForge svn server.

Also, can you clarify the release engineering process? Assuming development is now in the Github repo, I didn't see any release branches - only develop and master. How are they used? Are releases just snapshots you create at an appropriate time from one of these branches?

Keep up the great work!

Hi Dale,

Managing an open source project is a constant learning experience. The move from svn @ SF to git @ github is still a work-in-progress. There is another move I am anticipating as I learn more about git, and github as well.

The final resting place for the OpenDocMan code will be inside of <!-- m --><a class="postlink" href=""></a><!-- m -->, but until then, it is in the current spot at <!-- m --><a class="postlink" href=""></a><!-- m -->. I feel that OpenDocMan would be best served from it's own project page instead of a project in the Logical Arts page. I am in the process of gathering the docs on how to move the repo. I have also disabled the SVN @, I had enabled it temporarily while I moved the code to github and I forgot to turn it back off.

As for the release process, I am following a branching method described here: [url]

Hopefully that will explain the logic behind the Master and Develop branches.

Let me know if you have any other questions.

I added a new google group for development discussions:

<!-- m --><a class="postlink" href="!forum/opendocman-developers"> ... developers</a><!-- m -->

This will allow faster communication via email for development topics. is the new home for opendocman code.


Hi Stephen, thanks for clarifying (and for including the link to the workflow).

It seems most projects, no matter how close they come to the feature set I'm looking for, always require some site-specific tweaks. I'm trying to create a methodology for myself that preserves change management control, starting from the development project, through site-specific modifications, and all the way to deployment.

Now off to join the Google group....

That's why I added a plug-in architecture to OpenDocMan. Smile