From owner-freebsd-eclipse@FreeBSD.ORG Wed Jun 30 04:58:37 2010 Return-Path: Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBCD0106564A for ; Wed, 30 Jun 2010 04:58:37 +0000 (UTC) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (gerbercreations.com [71.39.140.16]) by mx1.freebsd.org (Postfix) with ESMTP id 8F8D68FC14 for ; Wed, 30 Jun 2010 04:58:37 +0000 (UTC) Received: from misty.eyesbeyond.com (localhost.eyesbeyond.com [127.0.0.1]) by misty.eyesbeyond.com (8.14.4/8.14.4) with ESMTP id o5U4watJ007975; Tue, 29 Jun 2010 21:58:36 -0700 (PDT) (envelope-from glewis@eyesbeyond.com) Received: (from glewis@localhost) by misty.eyesbeyond.com (8.14.4/8.14.4/Submit) id o5U4wZEO007974; Tue, 29 Jun 2010 21:58:35 -0700 (PDT) (envelope-from glewis@eyesbeyond.com) X-Authentication-Warning: misty.eyesbeyond.com: glewis set sender to glewis@eyesbeyond.com using -f Date: Tue, 29 Jun 2010 21:58:35 -0700 From: Greg Lewis To: Thomas Gellekum Message-ID: <20100630045835.GA93306@misty.eyesbeyond.com> References: <20100629152446.GA134@misty.eyesbeyond.com> <86mxudlqtv.fsf@siegel.tg.intern> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86mxudlqtv.fsf@siegel.tg.intern> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-eclipse@freebsd.org Subject: Re: eclipse-devel -> eclipse X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 04:58:37 -0000 On Tue, Jun 29, 2010 at 06:57:16PM +0200, Thomas Gellekum wrote: > Greg Lewis writes: > > Does anyone know of a showstopper that would prevent us from updating the > > current eclipse (3.4.2 IIRC) to what is currently in eclipse-devel (3.5.2)? > > > > If not then I'd propose to do that once the code freeze is over so that > > eclipse-devel can be used for people to work on 3.6.0. > > Well, my preference would actually be to ultimately have Helios (3.6.x) > as the default port, eclipse. It is the current release after all. > > For people who still need Galileo (3.5.x) I'd like the current > eclipse-devel repo-copied to eclipse35 or eclipse-galileo. You could > even do that for Ganymede (eclipse -> eclipse34 or eclipse-ganymede), > which eliminates any showstoppers. Unless someone is actually working on > an e4 port, eclipse-devel should then be IGNOREd (all IMHO, my 2c, ...). > > Of course, this could be done in several smaller steps, similar to what > you suggested above, so we can try out Helios in eclipse-devel for a > short while not breaking the default port. > > I realize this is quite a bit more work than your proposal, but I think > it's a good rule to have the current release as the default port. That is the idea. Copy eclipse-devel to eclipse to get that more up to date. Test out 3.6 in eclipse-devel then copy it over as well. -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org