I've been thinking about this for a while as people discussed the issues on the mailing lists.
Here are my opinions: 1. I think that http://wix.sourceforge.net/releases should be the place where we prop releases every time there is a "weekly" build of the WiX toolset. This should happen pretty much every Wednesday morning after a long Tuesday night of programming and integration by those of us in 98052. 2. I think the File Releases Page on Source Forge (http://sourceforge.net/project/showfiles.php?group_id=105970) should be reserved for builds that are verified by the community (in some way) to be "good". 3. We should find someone (not me, I'm already buried) to be the WiX Toolset Release Manager. That person would be responsible for gathering the feedback from the community to decide when to promote a weekly build to the Releases page. 4. I would also like to nominate for Frederik Carlier for the role of Release Manager. Note, that we only have so much disk space available for the weekly releases share. It will be necessary to promote a build to the Releases Page at least once every other month. What do people think? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frederik Carlier Sent: Saturday, April 15, 2006 4:53 PM To: [EMAIL PROTECTED] Subject: [WiX-devs] Automated SourceForge release process Hi all, I've managed to find a way to: - Add a new release to SourceForge; - Add files to a release; - Set properties of these files; I test-drove that utility uploading the releases that are on the WiX website to the SourceForge website. They are, however, still hidden because: - No release notes are added (because I don't have them); (note that release notes are not a hard requirement and the files can be made available for download without specifying them.) During the process a couple of releases got added by mistake. They have no files, are made hidden and thus do not show up on the downloads page. However, they do still make up for some clutter on the admin pages. I'm sorry. (But there was no way I could fully test without "going live"). The questions, however: How does the WiX team want to integrate this into their build process? Right now, the files get pulled of the WiX website and I enter some information while the program is running. That may or may not be appropriate, so let me know what you are looking for. In special, how do you want to deal with the password? Do you want to enter them manually while the program is running, have it as a command line parameter or something else? I need to clean up the code a little bit, and then I'll submit it to this list. Frederik. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
