Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 23974 invoked from network); 20 Feb 2010 17:41:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Feb 2010 17:41:21 -0000 Received: (qmail 7394 invoked by uid 500); 20 Feb 2010 17:41:20 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 7300 invoked by uid 500); 20 Feb 2010 17:41:19 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Delivered-To: moderator for user@couchdb.apache.org Received: (qmail 53270 invoked by uid 99); 17 Feb 2010 22:03:40 -0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApEBAPv0e0t20aDf/2dsb2JhbAAH2lCEXQQ Message-ID: <4B7C6783.1080103@skippinet.com.au> Date: Thu, 18 Feb 2010 09:02:43 +1100 From: Mark Hammond User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20100111 Lightning/1.0b1 Thunderbird/3.0.1 MIME-Version: 1.0 To: Noah Slater CC: user@couchdb.apache.org Subject: Re: Windows installer 0.10.1 References: <20100215091727.265030@gmx.net> <55047b711002151840q65579dd7j3ae5a458c5e4d781@mail.gmail.com> <4B7A5B62.4000907@griffinbyteworks.com> <20100216102257.171140@gmx.net> <4B7B28D3.3050603@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 18/02/2010 1:24 AM, Noah Slater wrote: > > On 16 Feb 2010, at 23:22, Mark Hammond wrote: > >> What needs to be done before a release can be considered 'official'? I'm happy to help do whatever is necessary to get an official 0.11 build for windows. > > A release artefact is considered official when it has been voted on by the community. > > The code that builds the Windows distribution artefact needs to be in trunk, and ideally integrated with the Autotools build system. All the above should be fine - the build process is fully integrated into trunk (and was before the 0.11 branch was cut) > Perhaps it makes sense to be able to run "make distsign" and have the regular tarball, as well as the Windows installer, placed in the root source directory. I'm not sure though, do you know of any projects that release UNIX-like tarballs and Windows installers? How do they do it? Most of the projects I am familiar with rely on someone with a windows machine making the windows build independently of the releases for other platforms. Specifically, the Windows binary build process is not a cross-platform build process, so making a release for all platforms from a single machine probably isn't viable. Thanks, Mark