Jake, thanks for supplying these links. This is my first time going through this, so I appreciate the assistance.
-- Rod Simpson @rockerston rodsimpson.com On June 17, 2014 at 8:27:04 PM, Jake Farrell ([email protected]) wrote: Rod If you are going to take on the release management please make sure you are familiar with [1] and [2] and all policies around the License and Notice files. Also the above artifacts you have outlined are not able to be apart of the source release (war, jar, gem) as they are binary files. -Jake [1]: http://incubator.apache.org/guides/releasemanagement.html [2]: http://incubator.apache.org/guides/releasemanagement.html#check-list On Tue, Jun 17, 2014 at 10:00 PM, Rod Simpson <[email protected]> wrote: > Usergridsters, > > This thread is to get the discussion ball rolling w/ respect to the > structure of our release artifact. > > I propose that we release as follows: > > 1. We only release one artifact (compressed archive - tar ball, zip, etc). > We previously discussed releasing everything (stack, sdks, portal) > separately, but after further discussions with many of you, the consensus > is that a single artifact would be more streamlined and user friendly. > > 2. The artifact will have a directory structure as follows: > > WebApps > - built portal code, in war file to be served off of Tomcat > - stack war file > - ideally, users can simply deploy what is in this directory to Tomcat > Lib > - sample usergrid props file > Launcher > - Jar file for launcher in separate dir > Docs > - docs describing how to get up and running w/ Usergrid > SDKs > - each SDK will be in its own subdirectory > UGC > - can’t forget our awesome command line utility > - should this include the UGC code? Or just a readme file telling how > to install (it is a Ruby Gem)? Or should we simply reference UGC in the > Docs? > > > Please weigh in. > > Rod > > > -- > Rod Simpson > @rockerston > rodsimpson.com
