-----Original Message----- From: sebb [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 7:01 PM To: general@incubator.apache.org Subject: Re: [VOTE] Approve Apache XAP 0.5.0 Release
On 11/03/2008, Bob Buffone <[EMAIL PROTECTED]> wrote: > > > -----Original Message----- > From: sebb [mailto:[EMAIL PROTECTED] > Sent: Monday, March 10, 2008 9:23 AM > To: general@incubator.apache.org > Subject: Re: [VOTE] Approve Apache XAP 0.5.0 Release > > On 10/03/2008, Bob Buffone <[EMAIL PROTECTED]> wrote: > > Incubator PM, > > > > The XAP team has put together a new release of the project (0.5.0) > and > > it has been approved by the xap-dev list with 8 (+1s) and 0 (others). > We > > > >It would be helpful to have a link to the vote thread. > > > http://www.g8l.us/49f > > > > > > > > are now asking the Incubator PM to approve this release so we can > > distribute it. > > > > The release candidate has been posted at: > > http://people.apache.org/~bbuffone/xap-release/0.5.0-incubator/ > > > > > >Which SVN tag was used for the release? > > > > > XAP_0.5.0 > >This seems to contain lots of files that are not in the archive: > >unittests/ Is used to run the unit tests on the project and we do not include them. >JSDoc-1.9.9.2/ Creates the documentation for the project and is also not included. > Also, some of the files in the archive are different from the tagged files, e.g. build-manufacturing.xml has two different versions. build.bat does not seem to be the same file at all buildUtil$py.class There seem to be a lot of class files in SVN - this is not usual. These files are not build from source but used in the build process when the JavaScript file concatenation and compression is performed. > > > >Where is the KEYS file containing the signer's public key? > > > > > http://svn.apache.org/repos/asf/incubator/xap/KEYS > > > > > >Is there a RAT report? > > > > > There is one, I have put it at > http://people.apache.org/~bbuffone/xap-release/0.5.0-incubator/rat_outpu > t.txt > > > > > >Normally there are separate source and binary archives. > > > > > Being that this is an Ajax toolkit, we have included all the source > files in the distribution to allow people to be able to customize the > application loading profile of their application. Users can either load > one large file upfront and make zero JavaScript requests later, or a > smaller upfront file and more JavaScript requests later. > >But does the archive need to contain the build files as well? The structure of the distribution file is as follows. dist - Contains the application structure a developer would need to be used as a starting point for developing a XAP application. docs - These would be the documentation files. samples - These are the sample showing people different features. source - Yes? These are all the source files that people use to build the xapcode.js files from the source included in the project. So I guess in a way we could separate these files into another (distribution file) and label it "-source.(zip)|(tar.gz). Would that make sense? >There seem to be several copies of some files, e.g. > >dojo.js.uncompressed.js >custom_rhino.jar >flash6_gateway.fla There will be one of these for each of the directories (samples, dist, source) >>Is it necessary to include both xapcore.js and xapcore.js.gz? >>Similarly for the other .js/.js.gz file pairs. It is necessary to include both of the files, it also the developer to use either in their application. We are including the three built files. xapcode.uncompressed.js - All JavaScript files concatenated in order of dependencies. xapcore.js - all files concatenated and compressed xapcore.js.gz - files concatenated, compressed and g-zipped >>Should the two "Thumbs.db" files be included? They look like Windows >>system files. The two thumb files should not be included in the release this is a mistake and thanks for catching that. > > Please cast your votes: > > > > [ ] +1 Release is approved > > [ ] -1 Veto the release (provide specific comments) > > > > Thank you, > > Bob (Buffone) > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
