On Thu, Apr 4, 2013 at 9:06 AM, Jasha Joachimsthal <[email protected]> wrote:
> On 4 April 2013 18:04, Matt Franklin <[email protected]> wrote: > > > On Thu, Apr 4, 2013 at 12:00 PM, Erin Noe-Payne < > [email protected] > > >wrote: > > > > > In other words, I would propose fixing the logged issues and > > > re-spinning the 0.21 release. Thoughts? > > > > > > > Given that our last release was a security fix, I think it would be good > to > > get things working properly and get 0.21 out the door. IMO, the console > > log thing is a problem and same with the Archetype issue Jasha filed. > Same > > goes for the mongodb issue Chris found. > > > > +1 for cancel, concentrated fix and respin in this instance. > > > > In that case, please keep the 0.21 tag, drop its artifacts from the repo > and create a new 0.21.1 release after the issues have been fixed. > > Jasha, I agree. > > > > > > > > > > > On Thu, Apr 4, 2013 at 11:24 AM, Erin Noe-Payne > > > <[email protected]> wrote: > > > > Reading the release process docs it looks like there are some > > > > repercussions for casting a -1 vote on a release, so I wanted to hold > > > > off before voting. However it looks to me like there are enough > major > > > > issues that we should resolve these before making the 0.21 release? > > > > > > > > On Thu, Apr 4, 2013 at 11:18 AM, Jasha Joachimsthal < > [email protected]> > > > wrote: > > > >> Found a minor issue. When you create a project from the archetype, > the > > > JDBC > > > >> setup is incorrect. It will build, but not run [1] > > > >> > > > >> Jasha > > > >> > > > >> [1] https://issues.apache.org/jira/browse/RAVE-949 > > > >> > > > >> > > > >> On 3 April 2013 20:27, Raminder Singh <[email protected]> wrote: > > > >> > > > >>> Discussion thread for vote on 0.21 release candidate. > > > >>> > > > >>> For more information on the release process, checkout - > > > >>> http://www.apache.org/dev/release.html > > > >>> > > > >>> Some of the things to check before voting are: > > > >>> - can you run the demo binaries > > > >>> - can you build the contents of source-release.zip and svn tag > > > >>> - do all of the staged jars/zips contain the required LICENSE and > > > NOTICE > > > >>> files > > > >>> - are all of the staged artifacts signed and the signature > verifiable > > > >>> - is the signing key in the project's KEYS file and on a public > > server > > > > > >
