yes, that's right. 2.2 users have everything they need in the distro. the 
update-install stuff will remain online to support the 2.1 users.

Dan


"Vinh Nguyen \(vinguye2\)" <[EMAIL PROTECTED]> wrote on 03/01/2007 
02:27:37 PM:

> So that means going forward with 2.2, we don't need to run
> update_install anymore, correct?  If later someone downloads 2.1 and
> runs update_install, it should only download 2.1 libs and not 2.2?  I
> just want to make sure that people can download different versions and
> test them separately.  Right now, although I agree that 2.1 should be
> the minimum release, no one can download the 2.0 distribution because
> running its update_install will actually download 2.1 libs.
> 
> 
> -----Original Message-----
> From: Daniel Jemiolo [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, March 01, 2007 11:20 AM
> To: [email protected]
> Subject: RE: Minutes of today's meeting
> 
> The plan is to keep the update-install stuff as it is now, so that 2.1
> users can pull down the required libraries. The decision to archive 2.0
> was made primarily because it depended on Axis2 1.1 snapshots that were
> made prior to changes (in Axis2 1.1) that prevented backwards
> compatibility; since most users would not want put snapshot code into
> production systems, we figured the best course of action would be to
> recommend 2.1 as the earliest release for users and archive 2.0 as a
> reference point. 2.2 and all future releases will have the libraries
> packaged in the distribution[1].
> 
> Dan
> 
> [1] http://marc.theaimsgroup.com/?l=muse-dev&m=117261884208990&w=2
> 
> 
> 
> "Vinh Nguyen \(vinguye2\)" <[EMAIL PROTECTED]> wrote on 03/01/2007
> 01:53:34 PM:
> 
> > Hi Dan,
> > One question about the update_install script.  When Muse 2.1 came out,
> 
> > and I ran update_install in my old 2.0 directory, it started 
> > downloading the 2.1 libs instead and overwrote the 2.0 libs.  Has this
> 
> > issue been resolved?  Allowing update_install to pull down libs for a 
> > particular Muse version will let people compare changes between the
> two.
> > -Vinh
> > 
> > 
> > -----Original Message-----
> > From: Daniel Jemiolo [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, March 01, 2007 8:42 AM
> > To: [email protected]
> > Subject: Minutes of today's meeting
> > 
> > Meeting Date: 
> > 
> >         3/1/07 11:00 a.m. EST
> > 
> > Attendees:
> > 
> >         Barry Atkins
> >         Andrew Eberbach
> >         Joel Hawkins
> >         Dan Jemiolo
> >         Balan Subramanian
> > 
> > Topics:
> > 
> > 1. Proposal to archive the 2.0 release
> > 
> > 2. Updates on any remaining questions/issues for 2.2 before code 
> > freeze
> > 
> > 
> > News & Decisions:
> > 
> > 1. Team approved proposal to archive 2.0 when 2.2 is released, making
> > 2.1 the earliest recommended distribution.
> > 
> >         a. The update-install files will need to remain in place even 
> > after 2.2 is released in order to support 2.1 users.
> > 
> > 2. Andrew and Joel are working on a small manifest/compilation problem
> 
> > related to MUSE-199. Once that is done, wsdl2java should be ready for 
> > RC.
> > 
> >         a. Barry will test the J2ME code generation (-osgi -mini). Dan
> 
> > will re-test J2EE code generation (-j2ee *).
> > 
> > 3. Barry has sent remaining J2ME docs using Muse HTML template. Dan 
> > will work this into the build for the RC.
> > 
> >         a. Remaining documentation updates are related to wsdl2java.
> > 
> > 
> > If you have any questions or clarifications about these minutes, 
> > please send them along!
> > 
> > 
> > 
> > 
> > 
> > 
> > Dan Jemiolo
> > IBM Corporation
> > Research Triangle Park, NC
> > 
> > 
> > +++ I'm an engineer. I make slides that people can't read. Sometimes I
> > eat
> > donuts. +++
> > 
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to