Current Version of Magmi also on Github

[andreasemer]

It would be cool, if the Github Repo would have the same Release (currently this is 0.7.18 on http://sourceforge.net/projects/magmi/ ) as on Sourceforge. It would be good, if there would be only one release (currently there are two folders with older releases in the Github Repo)

To provide older releases for users, it would be great to work with the Relase Feature of Git.

[dweeves]

Hi, the latest official release is 0.7.18 on sf, but the current github code is the base of "to be released" 0.7.19.
For the 0.8 folder, it's an artefact, i think i have create a new branch for this, it defines an evolution of the architecture to be able to handle different engines with the ability to share plugins or not.
Still thinking about the best "Git" way of doing things. i'm relatively new to Git.

[andreasemer]

In the most of my projects im working with Git-Flow http://nvie.com/posts/a-successful-git-branching-model/ and my favourite Git Client is http://www.sourcetreeapp.com/
Normally we are working in a "dev" branch, for bigger issues and storys we are creating feature branches, and merge the content if we have finished the task. Every time something goes live, we merge from "dev" in the "master" branch and we are creating Git releases.

[dweeves]

i'm working with eclipse & also some command line (to sync between sf git repo & github through a cron).
The main idea is to keep both "branches" active until 0.8 is not released (which may take time). I need to maintain 0.7.x for some time (at least until 0.7.19 but surely one or more bugfix releases after based on 0.7.x code).
I didn't touch 0.8 branch for some time now but i will as soon as i get time for.