I don't know enough about either maven or SVN for any of these. Does anyone else? I can add the dependency on the release plugin if that's going to be sufficient.
On Fri, Dec 12, 2008 at 11:36 AM, Chris Chabot <[email protected]> wrote: > If anyone would be willing to work on the below items, I would love to be > able to get new tarbals online today. > > - Create a RC1 tag > - Update the jar/war/pom/etc to reflect this version number > (1.0.0-rc1-incubating) > - Rename the packages created to > java-shindig-{source,binary}-FOO-incubating > - There were 2 bug reports which someone indicated he thought were > 'release blockers', discussion is ongoing on this > > Anything I left out? > > > On Fri, Dec 12, 2008 at 6:19 AM, Brian McCallister <[email protected]> > wrote: > > > On Thu, Dec 11, 2008 at 4:02 PM, Adam Winer <[email protected]> wrote: > > > On Thu, Dec 11, 2008 at 3:33 PM, Vincent Siveton > > > <[email protected]>wrote: > > > > > >> Hi guys, > > >> > > >> First, thanks for your efforts to make this first release happen! > > >> In summary, I suggest to correctly use Maven to create the artifacts, > > >> the main reason is to make reproducible artifacts. > > >> > > >> Here are my comments: > > >> - no tag has been created. The SCM connections in poms link to a > > >> branch. For this, I cast a -1 (no binding). > > > > > > > > > I believe the tag should only be created when we've got artifacts that > > have > > > passed muster, so there's a chicken-and-egg problem to point the SCM in > > the > > > pom at the tag. > > > > I strongly disagree with this statement -- have a tag for the rc, and > > copy the tag for the actual release. > > > > > > > > > > - POMS and parent POMs refer to 1.0.0-incubating-SNAPSHOT so -1 (no > > >> binding) too . Same for the content of the README. > > > > > > > > > Agreed - also, the MAINFEST.MF files refer to a Specification Version > and > > > Implementation Version as 1.0.0-incubating-SNAPSHOT, not > > 1.0.0-incubating. > > > > > >> > > >> - is it possible to share the full Maven repo? > > >> - following the rule "render to Caesar the things which are Caesar's", > > >> some committers are not presents in the pom (but in COMMITTERS file) > > >> +0 (no binding) > > >> - the war includes Shindig SNAPSHOTS -1 (no binding) > > >> - files insides the war (i.e. in WEB-INF/classes) doesn't include ASL > > >> -0 (no binding) > > >> - in the war, WEB-INF\classes\META-INF is not useful, +0 (no binding) > > >> - my understanding as Apache committer is that the NOTICE should > > >> include all use products, specially ICU and Json. Maybe have a glance > > >> to SHINDIG-725 to generate this file. > > >> - source code includes maybe unwanted System.out, see my comment [1] > > >> - finally, jira contains some issues for the 1.0.0-rc1 version -0 (no > > >> binding) > > >> > > >> Cheers, > > >> > > >> Vincent > > >> > > >> [1] > > >> > > http://shindig-dev.markmail.org/message/j6ztxtqhfcn4jyiz?q=+date:200812+ > > >> > > >> 2008/12/11 Chris Chabot <[email protected]>: > > >> > Hi All, > > >> > > > >> > I've prepared a set of tarballs for release, you can find them here: > > >> > http://people.apache.org/~chabotc/<http://people.apache.org/%7Echabotc/> > <http://people.apache.org/%7Echabotc/> > > >> > > > >> > The directory contains: > > >> > > > >> > - java-shindig-binary: the compiled .jar and .war files > > >> > - java-shindig-source: basically a tar of the complete source > > >> directory, > > >> > minus the php dir > > >> > - php-shindig: the complete set of files required to deploy the > php > > >> > version of shindig (php, features, javascript) > > >> > > > >> > And all of these in .tar.gz, tar.bz2 and .zip formats. > > >> > > > >> > The next step is for people to check these out, and give us your > > >> feedback, > > >> > please take some time to check the files that are relevant to you > > >> > (java-{source, binary} or php), see if they pass the RAT audit tool, > > if > > >> all > > >> > the files you would expect are in there (licence, notice, readme's > are > > in > > >> > order, etc), and that they actually work (!) > > >> > > > >> > If your in favor of submitting these to the > > >> > [email protected] list for voting of our > incubation > > >> > release, just replying with a +1 > > >> > is sufficient. > > >> > > > >> > If your not interested either way, voting +0 is appropriate to > reflect > > >> this. > > >> > > > >> > If you feel something is wrong with these files or that something > > should > > >> > have been done differently, please let us know! (accompanied with a > -1 > > >> > vote). > > >> > > > >> > We're hoping to get our release out before the holidays truly set > in, > > if > > >> we > > >> > can make that is largely dependent on how quick we can turn this > > around, > > >> > traditionally voting has a 72 hour window, so I'd like to close the > > >> voting > > >> > window by monday afternoon (72 hours from now). > > >> > > > >> > I look forward to your comments & can't wait to get our first > release > > >> out! > > >> > > > >> > -- Chris > > >> > > > >> > > > > > >
