Wouldn't we want to keep the config file on our website / SVN? It seems to me that placing the config file on any of the DISTS would be disasterious, as this contains the MD5 checksum that the app verifies to make sure the release wasn't tampered by the dist...
What are the thoughts on doing versioning in the config XML? have a version 1 node, version 2 node, etc. so that the app would look for a particular node, ignoring the rest of the config (so we can test future versions, or support old versions without an issue). -Nick On Tue, Jan 1, 2013 at 4:44 PM, Justin Mclean <jus...@classsoftware.com>wrote: > Hi, > > >> Would you consider the disclaimer page to be part of the source? > > The DISCLAIMER file is in the source kit for incubating releases. > I was referring to the disclaimer link in the application not the > DISCLAIMER file. > > > Source kits are (potentially filtered) dumps of what is in SVN. > And that correct with the installer, there's a source kit which someone > can take and compile the application. > > > I'm pretty sure Apache regulations would override any vote. > What "regulation" exactly? Can you point to me page that state that you > can't load XML files outside of it's SVN trunk? > > > This is potentially a legal issue > What is the legal issue here? The installer will be voted on and > distributed in the normal Apache Way (apache.org/dist). The XML file is > also in SVN at svn.apage.org that only Apache committers can access and > change. The installer will only download official Apache releases that have > been voted on and placed in apache.org/dist. > > I guess worse case a committer could modify the file XML file in SVN to > download another Apache binary kit but I think we would notice that and fix. > > Thanks, > Justin > >
