Return-Path: X-Original-To: apmail-archiva-dev-archive@www.apache.org Delivered-To: apmail-archiva-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4DE78104E4 for ; Wed, 1 May 2013 10:41:14 +0000 (UTC) Received: (qmail 89922 invoked by uid 500); 1 May 2013 10:41:13 -0000 Delivered-To: apmail-archiva-dev-archive@archiva.apache.org Received: (qmail 89717 invoked by uid 500); 1 May 2013 10:41:10 -0000 Mailing-List: contact dev-help@archiva.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@archiva.apache.org Delivered-To: mailing list dev@archiva.apache.org Received: (qmail 89688 invoked by uid 99); 1 May 2013 10:41:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 May 2013 10:41:09 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of odeaching@gmail.com designates 209.85.216.173 as permitted sender) Received: from [209.85.216.173] (HELO mail-qc0-f173.google.com) (209.85.216.173) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 May 2013 10:41:03 +0000 Received: by mail-qc0-f173.google.com with SMTP id b12so642560qca.32 for ; Wed, 01 May 2013 03:40:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=HPASFoFMNVnSAGIrQTVMw9cIYrVO8x8GYUcP1zrOL3w=; b=xNxMTiubCQJpgDjDjIw9xc8Jh3Wi0NixgzS6H380HhtZZYspuRAwnu3pGWjoE5djmA LblFjQrDpp3XxzItjmZMF9a7Lw3/2/Ic4cK63jgs3xAWgLuL/b8Vjq6k1W0nn3DWkQhw 7FImB4RPTysB1vSuQLPtog11zrL3Hyx6GyoOucd9XARgjiZzWCIX7T3vByKbss/9nKjB F00tvyX+nSP0T1kaCDw9HS6aRt5Y3qdZeA0Uw6uemkAX8J21rDOo/HVJ5qH+LoNq74+/ uFCyJZut1xnW32QrZGUzKZJSy45jS4FuwMNk1QE4MHGazI0NOBTZYXzN/Q5Lt5fIHg/V pkHg== MIME-Version: 1.0 X-Received: by 10.224.22.197 with SMTP id o5mr2644544qab.52.1367404843061; Wed, 01 May 2013 03:40:43 -0700 (PDT) Received: by 10.49.119.163 with HTTP; Wed, 1 May 2013 03:40:42 -0700 (PDT) In-Reply-To: <51752745.9090906@gmail.com> References: <5174EF06.2040005@gmail.com> <51752745.9090906@gmail.com> Date: Wed, 1 May 2013 18:40:42 +0800 Message-ID: Subject: Re: Releasing 1.4-M4 From: Deng Ching-Mallete To: "dev@archiva.apache.org" Content-Type: multipart/alternative; boundary=001a11c2cf46ef742d04dba5bff7 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2cf46ef742d04dba5bff7 Content-Type: text/plain; charset=ISO-8859-1 I'd like to add more audit logging (info, debug level) for easier debugging & trouble shooting for final 1.4.0 :) We can go through the tickets in 1.4-M5 and 1.4 buckets in JIRA and review each one then see if they're still applicable and/or critical for 1.4 final. Olivier, I can help you sift through them then we can discuss on the list which ones to keep in or out of 1.4? Thanks, Deng On Mon, Apr 22, 2013 at 8:04 PM, Sascha Vogt wrote: > Hi Olivier, > > what I meant was, focusing on getting a 1.4.0 out "fast", so remove > everything not absolutley necessary for a .0 release and move it to a > 1.4.1. > > I personally don't want anything more in a .0 - so from my point only > stabilizing and UI bugfixes (if there are any more issues, as said, will > check again after M4 is released) would be "needed". > > But obviously I don't have any say in this ;) that's why I asked, what > the timeline from the devs point of view is :) > > Greetings > -Sascha- > > Am 22.04.2013 13:05, schrieb Olivier Lamy: > > Hi, > > Currently our instance @apache is broken (my fault !! I fail an os > > upgrade). So I don't know when I will be able to start the release. > > > > Regarding roadmap, I added some new features for 1.4-M4 (regarding > > users/roles chaining) so I hope not too much bugs. > > IMHO a 1.4-M5 is possible with new fixes. > > Regarding what will be in the final 1.4.0, I have no idea maybe add a > > comment on what you will be happy to have in the release. (and better > > with a patch :P ) > > > > BTW sure after 1.4.0, I hope we will have 1.4.1 etc... > > > > > > > > 2013/4/22 Sascha Vogt : > >> Hi all, > >> > >> great to see progress on the 1.4 front ;) > >> > >> A general question: How is the roadmap for a 1.4 final release? I > >> currently see 89 issues in Jira "targeted" for either M5 or 1.4. Are > >> these all considered to be critical for a 1.4 final? > >> > >> The main point for asking is, that we're currently at 1.3.6 and have > >> quite a few pain points :) most of them are already fixed in 1.4 though > >> a few nasty UI issues prevent us currently from upgrading (though I must > >> admit I haven't looked at the latest M4 SNAPSHOT, will definitely try > >> the M4 release). > >> > >> As 1.4 makes huge improvements - wouldn't it be possible to figure out > >> what is critical to be in a 1.4.0 release, get that ready and out and > >> then improving it with 1.4.1 and so on? > >> > >> Greetings > >> -Sascha- > >> > >> Am 21.04.2013 11:37, schrieb Chris Graham: > >>> :-) > >>> > >>> I'll be sure to put it through it's paces! > >>> > >>> -Chris > >>> > >>> > >>> > >>> On Sat, Apr 20, 2013 at 11:15 PM, Olivier Lamy > wrote: > >>> > >>>> Sorry again for delay. > >>>> I will start slowly the release (redback-components/redback-core then > >>>> archiva) > > -- Maria Odea "Deng" Ching-Mallete | oching@apache.org | http://www.linkedin.com/in/oching --001a11c2cf46ef742d04dba5bff7--