[Gramps-devel] (no subject)

[Aaron R. S. <fuz...@ya...>]

upps I just realized I replied to the users list instead of copying the address sorry about that.

I just found out a few of us have been working on the windows installer project separately without collaborating. I was going to wait till I had finished reading the dev docs on the wiki and had better working code before I made an "announcement". also before I asked for the best way to commit code and release test packages. I'd would prefer to work together on things. I know were supposed to submit patches first and gain trust but I'd like to work together with him and swaping patches might be troublesome. could we have svn comit and just use a branch for our test code? How can we release test packages? Would it be best for us to start a windows exe / installer souceforge project first? I don't know if they still do but I know gimp did it that way for a while. We could always port the code into gramps later when it stablizes and the main devs want to include it with each release. 

Also I was wondering if we could change the name of the current "windows installer" to "windows source installer" My approach creates an actual exe and could be called the "windows binary installer" Unless someone has a better idea to differentiate the two. from what info I saw it appeared the main dev on the current windows installer isn't working on it much anymore. but I did notice the source for creating the installer had made it into svn and a 3.1.1 installer was released. so did someone pick it up?  I don't know about christians code but I know mine isn't ready for even a test package quite yet. though I hope to have one soon.