You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@archiva.apache.org by Brett Porter <br...@apache.org> on 2006/12/19 22:31:10 UTC
Getting together a release
Hi,
I am going to start looking into the issue with Archiva hanging on
repository.maven.org, then look at getting a release together, since
there has been a spike in interest and we can't really just recommend
people grab it from SVN.
Other than that issue, does anyone have any "must fixes" for a release?
- Brett
Re: Getting together a release
Posted by Jason van Zyl <ja...@maven.org>.
On 19 Dec 06, at 4:31 PM 19 Dec 06, Brett Porter wrote:
> Hi,
>
> I am going to start looking into the issue with Archiva hanging on
> repository.maven.org, then look at getting a release together,
> since there has been a spike in interest and we can't really just
> recommend people grab it from SVN.
>
> Other than that issue, does anyone have any "must fixes" for a
> release?
>
It must go back to an alpha, and I don't think it's even close to
being able to being released.
It's is totally unstable on central. Drawing in people to a release I
don't think is the right thing to do.
I will respond to your previous email about the design flaws but I
don't think a release is wise. It is totally not ready for a release
even as an alpha.
Jason.
> - Brett
>
Re: Getting together a release
Posted by Jason van Zyl <ja...@maven.org>.
On 19 Dec 06, at 9:14 PM 19 Dec 06, Joakim Erdfelt wrote:
> Jason van Zyl wrote:
>>
>> On 19 Dec 06, at 4:31 PM 19 Dec 06, Brett Porter wrote:
>>
>>> Hi,
>>>
>>> I am going to start looking into the issue with Archiva hanging on
>>> repository.maven.org, then look at getting a release together, since
>>> there has been a spike in interest and we can't really just
>>> recommend
>>> people grab it from SVN.
>>>
>>> Other than that issue, does anyone have any "must fixes" for a
>>> release?
>>>
>>
>> Two concrete show stoppers I think are that it doesn't convert
>> repositories properly. I've found several things and the groovy
>> conversion problem that cropped up a few days ago.
>>
>> Even on local setups Archiva will fall over. Joakim has found this
>> with his install and I have found it with mine.
>>
>> Over the course of December the only things that have been worked on
>> are Security, some conversion to common stuff, and the logo. No work
>> done on the conversion, the proxy, or the reporting. I just honestly
>> don't think it does anyone any service releasing it like this.
> I've been trying to get archiva pulled into a decent profiler so I can
> track down the apparent memory leak we have. The reason there hasn't
> been any commits is because I don't have a solution yet. ;-)
>
> As for the release. I think making an 1.0-alpha-1 release would be
> good
> at this point.
Yup, an alpha is fine.
> It will help if we have more people banging away at it.
> Having more test cases. Having more jiras around it. We know form
> our
> own testing what needs to be fixed. We can start with that list for
> 1.0-alpha-2. By then we'll hopefully have more input from other
> peoples
> out there.
>
Sounds perfectly reasonable.
Jason.
> - Joakim
>
Re: Getting together a release
Posted by Brett Porter <br...@apache.org>.
Ok, I'm now looking into it. I'll try and pull down central from
ibiblio at some point to do it locally, but I will likely muddle with
repository.maven.org too. Please let me know if that's a problem.
I have scheduled '1.0'. This reflects the 1.0-SNAPSHOT in the POM. It
is not the final version, we can bicker about its quality when the 72
issues get fixed. Or when we decide enough are fixed for it to be
released and well post poone the rest. I'm just interested in broad
scheduling for now.
All the things listed in this thread so far are there with a high
priority, except for the still vague 'design flaws' which I just
can't wait to hear about.
Cheers,
Brett
Re: Getting together a release
Posted by Carlos Sanchez <ca...@apache.org>.
I agree, having an alpha will only help with more eyes looking into it
On 12/20/06, Joakim Erdfelt <jo...@erdfelt.com> wrote:
> Jason van Zyl wrote:
> >
> > On 19 Dec 06, at 4:31 PM 19 Dec 06, Brett Porter wrote:
> >
> >> Hi,
> >>
> >> I am going to start looking into the issue with Archiva hanging on
> >> repository.maven.org, then look at getting a release together, since
> >> there has been a spike in interest and we can't really just recommend
> >> people grab it from SVN.
> >>
> >> Other than that issue, does anyone have any "must fixes" for a release?
> >>
> >
> > Two concrete show stoppers I think are that it doesn't convert
> > repositories properly. I've found several things and the groovy
> > conversion problem that cropped up a few days ago.
> >
> > Even on local setups Archiva will fall over. Joakim has found this
> > with his install and I have found it with mine.
> >
> > Over the course of December the only things that have been worked on
> > are Security, some conversion to common stuff, and the logo. No work
> > done on the conversion, the proxy, or the reporting. I just honestly
> > don't think it does anyone any service releasing it like this.
> I've been trying to get archiva pulled into a decent profiler so I can
> track down the apparent memory leak we have. The reason there hasn't
> been any commits is because I don't have a solution yet. ;-)
>
> As for the release. I think making an 1.0-alpha-1 release would be good
> at this point. It will help if we have more people banging away at it.
> Having more test cases. Having more jiras around it. We know form our
> own testing what needs to be fixed. We can start with that list for
> 1.0-alpha-2. By then we'll hopefully have more input from other peoples
> out there.
>
> - Joakim
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Getting together a release
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
Jason van Zyl wrote:
>
> On 19 Dec 06, at 4:31 PM 19 Dec 06, Brett Porter wrote:
>
>> Hi,
>>
>> I am going to start looking into the issue with Archiva hanging on
>> repository.maven.org, then look at getting a release together, since
>> there has been a spike in interest and we can't really just recommend
>> people grab it from SVN.
>>
>> Other than that issue, does anyone have any "must fixes" for a release?
>>
>
> Two concrete show stoppers I think are that it doesn't convert
> repositories properly. I've found several things and the groovy
> conversion problem that cropped up a few days ago.
>
> Even on local setups Archiva will fall over. Joakim has found this
> with his install and I have found it with mine.
>
> Over the course of December the only things that have been worked on
> are Security, some conversion to common stuff, and the logo. No work
> done on the conversion, the proxy, or the reporting. I just honestly
> don't think it does anyone any service releasing it like this.
I've been trying to get archiva pulled into a decent profiler so I can
track down the apparent memory leak we have. The reason there hasn't
been any commits is because I don't have a solution yet. ;-)
As for the release. I think making an 1.0-alpha-1 release would be good
at this point. It will help if we have more people banging away at it.
Having more test cases. Having more jiras around it. We know form our
own testing what needs to be fixed. We can start with that list for
1.0-alpha-2. By then we'll hopefully have more input from other peoples
out there.
- Joakim
Re: Getting together a release
Posted by Jason van Zyl <ja...@maven.org>.
On 19 Dec 06, at 4:31 PM 19 Dec 06, Brett Porter wrote:
> Hi,
>
> I am going to start looking into the issue with Archiva hanging on
> repository.maven.org, then look at getting a release together,
> since there has been a spike in interest and we can't really just
> recommend people grab it from SVN.
>
> Other than that issue, does anyone have any "must fixes" for a
> release?
>
Two concrete show stoppers I think are that it doesn't convert
repositories properly. I've found several things and the groovy
conversion problem that cropped up a few days ago.
Even on local setups Archiva will fall over. Joakim has found this
with his install and I have found it with mine.
Over the course of December the only things that have been worked on
are Security, some conversion to common stuff, and the logo. No work
done on the conversion, the proxy, or the reporting. I just honestly
don't think it does anyone any service releasing it like this.
Jason.
> - Brett
>
Re: Getting together a release
Posted by Max Bowsher <ma...@mxtelecom.com>.
Brett Porter wrote:
> Hi,
>
> I am going to start looking into the issue with Archiva hanging on
> repository.maven.org, then look at getting a release together, since
> there has been a spike in interest and we can't really just recommend
> people grab it from SVN.
>
> Other than that issue, does anyone have any "must fixes" for a release?
I don't remember where I saw it, but I think someone mentioned that the
proxying functionality was going to disappear from /proxy and be merged
into the /repository URLs. If that's correct, then getting such a major
URL change done before a release would be most desirable.
Other than that, the health report seems rather broken, in that is shows
a large quantity of errors which don't seem to correspond to reality, in
my experience. (see my message "Health Report woes" on archiva-users@).
If that's actually happening to everyone, not just me, then it probably
bears investigation before a release.
Max.