So my unsigned applet fix is not going in?
> -----Original Message----- > From: Daniel Rall [mailto:[EMAIL PROTECTED] > Sent: Friday, May 14, 2004 11:58 AM > To: [EMAIL PROTECTED] > Subject: 1.2 b2 release issues > > > Ryan Hoegg wrote: > > My +0 will graduate to +1 if we get current with Bugzilla. > Some bugs > > that look like 1.2 final material are 17789, 17665, 19620, > 19746, and of > > course 26386 (ASL 2.0). I am willing to jump in and help > out, what is > > everyone's feeling on post-1.2? I would like to do only > bugfixes on 1.2 > > and pull the applet code out into a separate build for 2.0. > Once that > > happens, we might consider Java 1.2 Collections for the rest? > ... > >> [ ] Yes, please proceed with the release (+1). > >> [X] Don't have an opinion or won't block the release (+0) > >> [ ] No (-1), because: ____________________________________________ > > Ryan, thanks for coming up with a strawman list. > > 17789 will be fixed by the next source tarball (of 1.2 b2 or > 1.2 final). Now > marked as such. > > 17665 looks like it requires numerous changes, including a > change to MinML. I'd > rather push out 1.2 with a release note for encoding > problems, and work on > fixing that in the 2.x or 1.3 series. > > 19620 was a no brainer, so I've committed a fix similar to > the one suggested by > Lee Haslup (which mirrors the duplicate code from the XmlRpc > class) to the 1.2 > and 2.0 streams, and marked the issue as fixed. > > 19746 had quite the hack proposed by Lee, but as it certainly > makes the code > less broken than it currently is, I've gone ahead and > committed it as a stop-gap > measure. Long term, 28982 nees to be implemented in its place. > > 26386 would be nice to have for 1.2, but is not something I > recommend holding up > the release for. Now, that said, there are a couple of > scripts floating around > which could resolve this quickly and easily, and I would love > someone to take > the initiative of emailing infrastructure@ and doing the conversion. > > > Andrew wrote: > > > > I have a small patch that a collegue is working on that I > would like > > to see on the 1.2 branch. It adds support for an input encoding to > > XmlRpc. This allows it to work correctly on z/OS and other EBCDIC > > systems, where the default encoding is EBCDIC but the network > > is ASCII. > ... > > Personally, I don't see this as essential for the 1.2 > release, but am very much > in favor of including this in the code base. My strawman > suggestion is to ship > 1.2 without it, and ship a subsequent 1.3 with -- possibly -- > only this change. > I have no compunction about this being committed to the 2.0 > stream immediately. > > [I have a separate email out to Andrew about getting his new > key installed.] > > > We've been running 1.2 quite successfully with customers for > > a while now. We don't use the XmlRpcServer/XmlRpcWorker > > stuff though. > > What do you use instead? > > - Dan >
