Re: Releasing 1.4-M4
On Wed, May 1, 2013 at 6:43 PM, Olivier Lamy wrote: > 2013/5/1 Deng Ching-Mallete : > > 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...) > Yep, more debug statements in various classes. I'll add more notes in the ticket I filed for this. > > > > > 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 > Cool :-) -Deng > > > > 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 | och...@apache.org | > > http://www.linkedin.com/in/oching > > > > -- > Olivier Lamy > Ecetera: http://ecetera.com.au > http://twitter.com/olamy | http://linkedin.com/in/olamy > -- Maria Odea "Deng" Ching-Mallete | och...@apache.org | http://www.linkedin.com/in/oching
Re: Releasing 1.4-M4
2013/5/1 Deng Ching-Mallete : > 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 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 | och...@apache.org | > http://www.linkedin.com/in/oching -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Releasing 1.4-M4
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 | och...@apache.org | http://www.linkedin.com/in/oching
Re: Unable to download an artifact (apache-archiva-1.4-M3-js-bin)
Hi Piotr, The problem occurs if the URL specified in the Application Link in UI Configuration has a trailing '/' at the end of it. Workaround is to remove the '/' in the URL (e.g. http://artifacts.repository.com instead of http://artifacts.repository.com/). Thanks, Deng On Tue, Apr 30, 2013 at 6:02 PM, Deng Ching-Mallete wrote: > Hi Piotr, > > Thanks for the additional details :) > > Btw, you can create an account in Codehaus (including jira) from here: > > http://xircles.codehaus.org/signup > > I've just filed the issue that you reported in JIRA, please see > https://jira.codehaus.org/browse/MRM-1757 > > Thanks, > Deng > > > On Tue, Apr 30, 2013 at 3:53 PM, Piotr Szwed wrote: > >> Hi Deng, >> >> I would be happy to raise a ticket, but I do not have Jira account yet. >> >> Jira says: "Not a member? To request an account, please contact your JIRA >> administrators." - Who can help me with that ? >> >> My use case is an unusual - I am going to use Archiva as a binary files >> storage/backend for Gerrit (https://code.google.com/p/gerrit/). My >> experimental implementation and testing might be a valuable input for you, >> so Jira account is greatly appreciated :) >> >> Regards, >> -- >> Piotr Szwed >> >> >> On Mon, Apr 29, 2013 at 5:25 PM, Piotr Szwed wrote: >> >> > Hi All, >> > >> > I am trying to introduce Archiva to one of my clients. >> > >> > After uploading an artifact to the newly created repository, I am unable >> > to download it. The problem seems to be in the URL generated by Jetty. >> > >> > When I click on the particular artifact's URL, I get the following link: >> > *//* >> > >> repository/playground/com/gerrit-architecture/1.0/gerrit-architecture-1.0.zip >> > >> > which results with the following message: >> > >> > *Problem accessing >> //repository/playground/com/gerrit-architecture/1.0/gerrit-architecture-1.0.zip. >> > Reason:Not Found* >> > After removing the first slash "/" from the URL - downloading >> > starts automatically. So I suspect that one of the "/" is redundant and >> > shouldn't be generated. >> > >> > my default config entry seems to be fine: >> > >> > >> > >> ./conf/archiva.xml:/mnt/localdata/gerrit/archiva/apache-archiva-js-1.4-M3/repositories/playground >> > >> > >> > Is it a known bug? Are there any plans to fix it with 1.4m4 ? This is a >> > blocker to me :( >> > >> > Thanks ! >> > >> > -- >> > Piotr Szwed >> > >> > > > > -- > Maria Odea "Deng" Ching-Mallete | och...@apache.org | > http://www.linkedin.com/in/oching > > -- Maria Odea "Deng" Ching-Mallete | och...@apache.org | http://www.linkedin.com/in/oching
