On Tuesday 20 January 2004 6:00 pm, Daniel F. Savarese wrote: > In message <[EMAIL PROTECTED]>, Jeffrey D. Brekke writes: > >I think any committer could be the release manager, +1. > > > >I haven't had time to look at the code changes deeply. Based on what > >I've seen and what was discussed, I'm +0 on the release of 1.2.0, but > >I do think that a jdk 1.1 compatible version release at the same time, > >if not before 1.2.0, should be considered. > > I'm in a real time bind right now and have not read all of the emails > related to Commons Net, although I've got them saved up for later > examination (I noticed Rory Winston submitted more NNTP enhancements; > we should discuss voting him as a committer after we get past the > immediate business). If a vote is needed for a release manager, I > assumed my vote was implicit based on my earlier comments. Here's an > explicit +1 for Steve to manage the release. I haven't had time to > look at the most recent changes. I was +1 on a 1.2 release to > acommodate Ant's release schedule based on the changes up to Steve's > take on resolving the VMS parser situation, even though I believed we'd > have to deprecate some of the stuff later. I'd rather err on the side > of being user-driven and meeting user needs than insist on perfection. > However, additional changes were made that I haven't had time to examine > (Steve's refactoring) and I believe will require more time to discuss. > So if I have to vote right now I'm: > +1 on a 1.2 release if we don't include those latest changes > +0 if we do > I'm also +1 on the JDK 1.1 compatible 1.1.1 maintenance release. I > think we've got three +1's on this one (scohen, jbrekke, dfs), so > all that's needed is to start a vote thread with a release plan > specifying the release criteria (i.e., remove JDK 1.1 incompatibilities > in the 1.1 release) cc'ed to the PMC and giving anyone an opportunity > to -1 it. > > I tried to anticipate and qualify what I could since I'm lagging behind > on email and may not be able to respond in a timely manner over the > next week. > > daniel >
Okay. I will work on the 1.1.1 release. That should be a fairly simple one for me to "practice" on - it will be my first. The one I'm really interested in is 1.2.0. I don't think it makes any sense to release 1.2.0 without my latest changes, because as you said earlier, we'd be adding a lot of new junk that will then have to be deprecated later. The latest stuff is much cleaner and should get us out of the deprecation business for awhile. So, I'd say, I'd rather wait until Daniel and Jeff can take a look at it, and then I'd like to do a release of 1.2.0 with that included. An additional issue is whether or not to include Rory Winston's NNTP patches in 1.2.0. I am +0 on that, having no way to evaluate that one. Do we have tests for it? I will defer to you guys on this one. If, after we're ready to commit the rest of 1.2.0, we can include that too, or not, as you decide. Fair enough? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
