2013/5/1 Deng Ching-Mallete <[email protected]>: > I'd like to add more audit logging (info, debug level) for easier debugging > & trouble shooting for final 1.4.0 :) wdym exactly ? more debug statement in various classes ? (maybe create some markers to help ? managed-repository, artifacts-read etc...)
> > 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? sure > > Thanks, > Deng > > > On Mon, Apr 22, 2013 at 8:04 PM, Sascha Vogt <[email protected]> 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 <[email protected]>: >> >> 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 <[email protected]> >> wrote: >> >>> >> >>>> Sorry again for delay. >> >>>> I will start slowly the release (redback-components/redback-core then >> >>>> archiva) >> >> > > > -- > Maria Odea "Deng" Ching-Mallete | [email protected] | > http://www.linkedin.com/in/oching -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy
