Gianugo Rabellino wrote: > > Carsten Ziegeler wrote: > > > To really get the final release out asap, we should identify all > > showstoppers. > > Currently entered in bugzilla are two blockers (I fixed the > third one (5051) > > recently). > > > > Here is the list from bugzilla: > > ------------------------------ > > ID Sev Pri Plt Owner State Result Summary > > 5060 Blo Oth PC [EMAIL PROTECTED] NEW Poorly formed > filesystem URL > > with file:// issues > > 5063 Blo Oth Oth [EMAIL PROTECTED] NEW Distribution > .war broken in > > Tomcat 4 > > > > I think, at least, #5060 is a real blocker, #5063 should be > easily fixed by > > changing the build scripts or adding some comments etc. > > > > If we can't fix 5060 very quickly, what about disabling the resolver for > > the final release? This would make 2.0 "block bug free". We could work > > on that "new" feature and make a 2.0.1 (or whatever) with a working > > resolver. > > > +1 on this.We need to get out with a release RSN. > > Also, what about having a list of changes that are in 2.1 only and > need/should be ported to the final release, run a vote against them (as > it was done before beta) and decide about them? > As far as I can see, there should nothing more need a backport. We did so already with most of the required features. I know, you will say now: And what about the configurable SourceHandlers? Well, I'm +0 on this.
Carsten > Ciao, > > -- > Gianugo > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
