From codesprints-bounces@ietf.org Fri Dec 12 02:54:34 2008 Return-Path: X-Original-To: codesprints-archive@ietf.org Delivered-To: ietfarch-codesprints-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5B7873A6AAA; Fri, 12 Dec 2008 02:54:34 -0800 (PST) X-Original-To: codesprints@core3.amsl.com Delivered-To: codesprints@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7D1083A6AAA for ; Fri, 12 Dec 2008 02:54:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.46 X-Spam-Level: X-Spam-Status: No, score=-6.46 tagged_above=-999 required=5 tests=[AWL=0.139, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2qKkjDpqXcf6 for ; Fri, 12 Dec 2008 02:54:31 -0800 (PST) Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id 613A33A6ABA for ; Fri, 12 Dec 2008 02:54:31 -0800 (PST) Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id mBCAsKx2014909; Fri, 12 Dec 2008 12:54:22 +0200 Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 12 Dec 2008 12:54:19 +0200 Received: from vaebe104.NOE.Nokia.com ([10.160.244.59]) by vaebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 12 Dec 2008 12:54:19 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 12 Dec 2008 12:54:18 +0200 Message-ID: <1696498986EFEC4D9153717DA325CB72028BA89F@vaebe104.NOE.Nokia.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [codesprints] Future sprint work Thread-Index: AclLTdI9NR27q272Rfum8IsixkONmgQ995ZA References: From: To: , X-OriginalArrivalTime: 12 Dec 2008 10:54:19.0389 (UTC) FILETIME=[FBCF9AD0:01C95C47] X-Nokia-AV: Clean Subject: Re: [codesprints] Future sprint work X-BeenThere: codesprints@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "List for coordinating \(and following up on\) codesprint activities" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: codesprints-bounces@ietf.org Errors-To: codesprints-bounces@ietf.org Replying a bit late, but... It would be really nice if we could do this incrementally, taking some changes to use before fully upgrading to 0.96. This would split the effort to more manageable pieces, and probably would be safer, too. It seems some of these changes could be done while still using 0.96: e.g. much of the Unicode work, and changing "maxlength" to "max_length" for model fields (it seems both spellings should work with 0.96). Some parts (like the new admin framework) could probably be done with "if django.VERSION[0] == 1" style (which would be removed after 0.96 wasn't supported any more). The new admin interface code wouldn't get run on 0.96, but it would avoid having two diverging branches. On the other hand, I don't yet have a good picture of what amount of changes would be needed to allow even simple testing with Django 1.0 (where at least some views/URLs would work, even if not everything). Does anyone know? Best regards, Pasi > -----Original Message----- > From: Robert Sparks > Sent: 20 November, 2008 22:23 > To: codesprints@ietf.org > Subject: [codesprints] Future sprint work > > One of the things we noted before this sprint was the need to > migrate to Django 1.0 at some point in the future. > > When time allows, please look over > http://docs.djangoproject.com/en/dev/releases/1.0-porting-guide/ > (does anyone have additional/better information on this topic?). > > With that information in hand, do you think setting a goal to be on > 1.0 before (or at) the next sprint is reasonable? > > RjS _______________________________________________ codesprints mailing list codesprints@ietf.org https://www.ietf.org/mailman/listinfo/codesprints