Hi, The good news is that if one prepares their environment for BrowserMap [3] (e.g. had Node.js installed and two global plugins) the release can be done as simple as grunt package, which ends up with a zip file containing the sources and the dist files - browsermap-<release_number>.zip - with the following structure:
LICENSE NOTICE README.md demo/css/style.css demo/index.browser.html demo/index.highResolutionDisplay.html demo/index.html demo/index.oldBrowser.html demo/index.smartphone.highResolutionDisplay.html demo/index.smartphone.html demo/index.tablet.highResolutionDisplay.html demo/index.tablet.html demo/js/browsermap.min.js demo/js/showcase.js doc/BrowserMap.html doc/BrowserMapUtil.CookieManager.html doc/BrowserMapUtil.File.html doc/BrowserMapUtil.Url.html doc/BrowserMapUtil.html doc/Cookie.html doc/bmap.js.html doc/bmaputil.js.html doc/index.html doc/scripts/linenumber.js doc/scripts/prettify/Apache-License-2.0.txt doc/scripts/prettify/lang-css.js doc/scripts/prettify/prettify.js doc/styles/jsdoc-default.css doc/styles/prettify-jsdoc.css doc/styles/prettify-tomorrow.css libs/browsermap/bmap.js libs/browsermap/bmaputil.js libs/browsermap/devicegroups.js libs/browsermap/probes.js libs/externals/matchMedia/matchMedia.js libs/externals/modernizr/modernizr.custom.js libs/browsermap.min.js If that needs to end up as part of a process to release all the modules at once we'd need some scripts (preferably platform independent or provided for all major platforms) to handle this. IIRC all BrowserMap's files contain the ASF header (this was done just prior to donating the code to ASF) and I've also made sure to include the appropriate LICENSE and NOTICE files since this module has its own public github mirror for TravisCI integration. Please let me know how can I be of help. Thanks, Radu [3] - https://github.com/apache/devicemap-browsermap#development Radu Cotescu | Software Engineer, Tech Blogger, Author Web:radu.cotescu.comEmail:[email protected]:+40 744 406 353 On Mon, Sep 30, 2013 at 3:53 PM, Bertrand Delacretaz <[email protected] > wrote: > Hi Radu, > > On Mon, Sep 30, 2013 at 2:41 PM, Radu Cotescu <[email protected]> wrote: > > ...Do we need to do anything special for BrowserMap? We have a demo > running > > with version 1.3.0 at [1]. The version number is maintained at [2]... > > For a proper Apache release we need to publish an immutable archive of > the code under http://apache.org/dist/incubator/ > > That archive needs to follow the rules defined at > http://www.apache.org/dev/release.html, in this case that's mostly: > > -Include a NOTICE and LICENSE file as described there > > -Each file that's released (except "trivial non-creative files") > includes the Apache License header. > > Ideally we should have an automated build that produces the browsermap > release archive - I've never done that for non-Java code here, if you > need examples I'd look at Cordova or other projects which release > javascript code. > > HTH, > -Bertrand >
