Also you could add that mod_jk 1.2.0 is in final stage and will be release in the next 2 weeks ....
- Henri Gomez ___[_]____ EMAIL : [EMAIL PROTECTED] (. .) PGP KEY : 697ECEDD ...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 >-----Original Message----- >From: Ignacio J. Ortega [mailto:[EMAIL PROTECTED]] >Sent: Wednesday, June 26, 2002 10:04 AM >To: 'Jakarta General List' >Subject: RE: [PROPOSAL] Newsletter Submissions > > >Hola Rob: > >Another history from tomcat-dev: > >jk2 ( the next version of jk connector) is reaching Alpha state, there >is not dates in our plan, but doesnt seem very dare, to say >that will be >ready for release in 2 months or so, more or less in >september.. will be >apr based, supporting ( in his first release ) at least the 3 major >webservers, Apache 1.X, Apache 2.X and IIS 4.0 and up.. > >Saludos , >Ignacio J. Ortega > > >> -----Mensaje original----- >> De: Rob Oxspring [mailto:[EMAIL PROTECTED]] >> Enviado el: 25 de junio de 2002 12:47 >> Para: [EMAIL PROTECTED] >> Asunto: [PROPOSAL] Newsletter Submissions >> >> >> Id like to propose the following time scale for the June >> newsletter and >> similar setup for subsequent ones. >> >> 1) Content submissions in by end of sunday (midnight) >> >> 2) I'll pull together whats there and post a draft copy to >> general@ on >> the Monday (1st July) >> >> 3) Then await edits and a lazy consensus and post final copy to >> announcements@ on the Wednesday (3rd July) >> >> Content should aim to summerise what's been going on in the >> various groups >> throughout June, I used the most active threads for issue #0 >> (http://nagoya.apache.org/eyebrowse/ReadMsg?listName=general@j >akarta.apache. >org&msgNo=12130) but this may miss out the occasional worthy decision / >change / vote, YMMV. It would also be good to all be using the same >reference source so nagoya.apache.org/eyebrowse for links to mail >archives >where possible? > >I guess submissions might as well go directly to me so that the draft >has >something new for people to read. Although as Ted Husted suggested - >discussion of content in the respective -dev lists would probably be a >good >step prior to submission, and some sort of [news] subject prefix would >be >appreciated for filtering. If projects want to further subdivide (e.g. >commons / avalon) then they should organise it amongst themselves. > >Could I have volunteers to organise / edit / submit on behalf of each >-dev >list for June? I'd like to avoid a cross-post invitation to >all -dev@ if >at >all possible. > >Rob > > >-- >To unsubscribe, e-mail: ><mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: ><mailto:[EMAIL PROTECTED]> > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
