Hi Lieven,

It's not difficult to upload code to SourceForge (I've had other projects on there), the problem is I don't have access (username/password) to the MH project.

I'm not sure if Mark/Jim do and they can add a fewe more of us as admins?


On Fri, Jul 19, 2013 at 2:10 PM, Michael Stovenour <michael@stovenour.net> wrote:

On July 18, 2013 4:10 PM Lee wrote:



Hi Lieven,

That SourceForge page ( http://misterhouse.sourceforge.net/ ) actually points to the v3.00 zip even though it says v2.200.

My issue is with the http://sourceforge.net/projects/misterhouse/?source=directory page that still lists the last version that was built on SourceForge v2.103 (sorry misread it before) that dates back to 2008... Looks bad...

It could really do with a newer zip uploading there... Or the whole project page just taking down...


Do you know how to upload a new zip release to sourceforge?   If you can find the instructions I’ll add that as a step in the “release process”.   There were objections to abandoning sourceforge outright because many web pages link to there for MisterHouse.  IMO, it would be ideal if we could continue to provide the “latest stable” release there in addition to keeping the documentation updated.


I would also add that there was a reason for the 'Stable' release of MH, things go wrong sometimes weeks after release and non-devs don't need the aggro that goes with bleeding edge code, hence the stable and latest releases in the old system.

I think we have this covered….  We have two branches on GitHub, stable and master.  Master is where we push all the bleeding edge code.  Stable is a major release (possibly with patches for bugs but I haven’t seen a process for patching stable yet).  Is this what you mean or are you implying we need two stable versions (i.e. stable and stable-1)?