Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 32488 invoked from network); 6 Jun 2008 16:15:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Jun 2008 16:15:31 -0000 Received: (qmail 68176 invoked by uid 500); 6 Jun 2008 16:15:33 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 68110 invoked by uid 500); 6 Jun 2008 16:15:33 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 68099 invoked by uid 99); 6 Jun 2008 16:15:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jun 2008 09:15:33 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kevan.miller@gmail.com designates 209.85.146.177 as permitted sender) Received: from [209.85.146.177] (HELO wa-out-1112.google.com) (209.85.146.177) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jun 2008 16:14:43 +0000 Received: by wa-out-1112.google.com with SMTP id j40so817003wah.1 for ; Fri, 06 Jun 2008 09:15:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :in-reply-to:content-type:mime-version:subject:date:references :x-mailer; bh=9yGw3VG6dNK2LvRkuNfyKwm6cq30XrpUoZt7pyYrvzI=; b=BrUIH40V7AWVM+CEOmVxbbbSghJLeLdHJdMEDo+42TLMkmKe3pUJGNOohlLQ3Rjs/k iMc9KbkeiGc0pK/44uC2ZNWl8KqUNuUySb1wjDvPqh25q8gq9OA3dq5yV2EZMS6UsN2E 6Zb1DVK7vsh0bd8wcUB2GPHfVQMdFXUmsd39Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type:mime-version:subject :date:references:x-mailer; b=LKDVqhniCK20YO9ryMX8JDdQuzQb63TtTe8j30FGh/rNYQrlEpwh446nCbVPLoIRZa WepPlCKJVug5vi/bJfxCzQbwKd832VNwqIZfY/6k5FsSm4H0ywH7suxlStNAYbrnUiGC lotYqg9Sq8M8XA37klbQnTF8CS9wPVnIA2phM= Received: by 10.115.79.8 with SMTP id g8mr306568wal.215.1212768897063; Fri, 06 Jun 2008 09:14:57 -0700 (PDT) Received: from ?10.0.1.186? ( [65.190.205.55]) by mx.google.com with ESMTPS id 30sm4814056yxk.4.2008.06.06.09.14.56 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 06 Jun 2008 09:14:56 -0700 (PDT) Message-Id: From: Kevan Miller To: dev@geronimo.apache.org In-Reply-To: <73a75e430806060852p79908a56o5afc02a6b9633334@mail.gmail.com> Content-Type: multipart/alternative; boundary=Apple-Mail-21-385977813 Mime-Version: 1.0 (Apple Message framework v924) Subject: Re: Upgrading to Dojo 1.1.1 Date: Fri, 6 Jun 2008 12:14:55 -0400 References: <73a75e430806060852p79908a56o5afc02a6b9633334@mail.gmail.com> X-Mailer: Apple Mail (2.924) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-21-385977813 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit On Jun 6, 2008, at 11:52 AM, Jason Warner wrote: > Would this let us remove Dojo 0.4.3 from the server or would we keep > it there for users who might still be using it? If so, how long are > we going to do that for? My vote would be to yank it out after > we're no longer dependent on it, but I'm not sure what the community > at large would think of that. Regardless, I like your idea, Joe. IMO, we would drop 0.4.3. I don't think we maintained for backward compatibility reasons, more because we didn't want to update the admin console code, at that point in time. I think it would be good to upgrade to 1.1.1. I also assume it would replace the current 1.0.2 version? Perhaps we should consider encoding the dojo version in the dojo path name. I'd prefer to see this work broken down into reasonable chunks (where possible), so that we can track progress (and others can participate). First add /dojo-1.1.1 and start incrementally moving code over to use new dojo. I don't know the internals of the admin console. So, not sure how well that work breaks down into manageable chunks. --kevan > > > +1 > > On Fri, Jun 6, 2008 at 11:04 AM, Joseph Leong > wrote: > Hi everyone, > > I've been tossing the idea around in my head of taking the > initiative to upgrade the current items written in Dojo to 1.1.1, I > know we still have some Dojo 0.4.3, which isn't supported anymore, > in use and there has been vast improvements with their new Dijit > package for widgets among many other items. Also, with some > recently reported JIRAs about accessibility compatibility being an > issue in these Dojo components we can make use of the a11y available > in it. Overall, i also think we might also benefit a cleaner setup > from streamlining our versions in terms of future development and > maintenance as well. > > Although I haven't looked in complete detail in each of the AG Dojo > pieces, i know that the 0.4.3 transition to 1.1.1 will take some > work because the widget system has been separated out to it's own > pieces (diji) and so simple work arounds will not do. That is, this > will be a big block change rather than an incremental one. > > Does anyone have any thoughts - one way or the other on this > undertaking? > > > Thanks! > Joseph Leong > > > > -- > ~Jason Warner --Apple-Mail-21-385977813 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable
On Jun 6, 2008, = at 11:52 AM, Jason Warner wrote:

Would this = let us remove Dojo 0.4.3 from the server or would we keep it there for = users who might still be using it?  If so, how long are we going to = do that for?  My vote would be to yank it out after we're no longer = dependent on it, but I'm not sure what the community at large would = think of that.  Regardless, I like your idea, = Joe.

IMO, we would drop 0.4.3. I don't = think we maintained for backward compatibility reasons, more because we = didn't want to update the admin console code, at that point in = time.

I think it would be good to upgrade to = 1.1.1. I also assume it would replace the current 1.0.2 version? Perhaps = we should consider encoding the dojo version in the dojo path = name.

I'd prefer to see this work broken down = into reasonable chunks (where possible), so that we can track progress = (and others can participate). First add /dojo-1.1.1 and start = incrementally moving code over to use new dojo. I don't know the = internals of the admin console. So, not sure how well that work breaks = down into manageable = chunks. 

--kevan



+1

On Fri, Jun = 6, 2008 at 11:04 AM, Joseph Leong <josephcleong@gmail.com> = wrote:
Hi everyone,

I've been tossing the idea around in my head = of taking the initiative to upgrade the current items written in Dojo to = 1.1.1, I know we still have some Dojo 0.4.3, which isn't supported = anymore, in use and there has been vast improvements with their new = Dijit package for widgets among many other items.  Also, with some = recently reported JIRAs about accessibility compatibility being an issue = in these Dojo components we can make use of the a11y available in = it.  Overall, i also think we might also benefit a cleaner setup = from streamlining our versions  in terms of future development and = maintenance as well.

Although I haven't looked in complete = detail in each of the AG Dojo pieces, i know that the 0.4.3 transition = to 1.1.1 will take some work because the widget system has been = separated out to it's own pieces (diji) and so simple work arounds will = not do.  That is, this will be a big block change rather than an = incremental one.

Does anyone have any thoughts - one way or the = other on this undertaking?


Thanks!
Joseph Leong



--
~Jason = Warner

= --Apple-Mail-21-385977813--