Hi guys, now that the 2014.03 is released, I will switch to a more clear GitHub setup to be able to both contribute to MITK while having my own local changes. I checked whether my application builds with the new release (before, I worked with the master branch of MITK/MITK). Everything went well apart from one small thing - http://bugs.mitk.org/show_bug.cgi?id=16848 - I reported this bug a while ago. Since the change is trivial and (likely) won't raise too much discussion I created a pull request with the fix: https://github.com/MITK/MITK/pull/56
I think that after I give a good run for my setup - I could write a simple guide for GitHub-based development with MITK which would include: - Forking MITK repo with a stable release tag - Setting up major branches, e.g. "stable" and "development", where stable would contain the MITK code guaranteed to work with "MyApp" and "development" is for syncing changes between multiple developers of "MyApp" and/or pulling from original MITK repository for testing a new release or particular features needed before the next release - Branching the "development" branch to introduce changes - that can be directly related to the bug in MITK or later renamed after testing a solution and filing a bug. - Contributing to MITK - creating pull request based on branches from "development" branch So the question is: are the users of MITK at all interested in such a guide and would the developers like to include this to the original MITK docs/website? Cheers, Rostislav. ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
