I think we should "just release" it as it is and take it from there. The snapshot-version has been in use for quite a while now.
Last issue to resolve would be https://issues.apache.org/jira/browse/NPANDAY-599 Brett, you talked about somehow caching the resolver per project. I think if that's done we're fine and can close 599 and thus 402. -----Ursprüngliche Nachricht----- Von: Brett Porter [mailto:br...@porterclan.net] Im Auftrag von Brett Porter Gesendet: Donnerstag, 21. August 2014 02:43 An: npanday-dev@incubator.apache.org Betreff: Re: Release 1.5.0 ?? Thanks for the review and the nudge here Konstantin. I've just dropped a couple out, and will take a quick pass over the non-blockers and ones assigned to me to see what else can be closed or bumped. Do any others have a moment to look through them? Thanks, Brett On 19 Aug 2014, at 7:37 am, Konstantin Boudnik <c...@apache.org> wrote: > Ladies and gentlemen. > > I've pocked around a little bit and it seems that there are only 4 > tickets (of which only 2 are real blockers) are effectively standing > between today and the next release of the project. One of the critical is also an improvement. > > Here's what I am referring to http://is.gd/WzgibS > > I am thinking if this would be a sane idea to deal with the blockers > and push Major bugs into 1.6-incubating? This tactic will help to get > the release out so the users have something new to work with. And it > also will provide a new development baseline for the contributors? > > What do you guys think? > Cos >
