> GIS is a bit of a special case; Justin Bronn is the maintainer there,
> and he and the rest of the GeoDjango contributors develop somewhat
> independently of the rest of Django.
>
> That said, they don't get any special exemptions in terms of timeline,
> so GeoDjango feature freeze is this
On Thu, Mar 19, 2009 at 6:11 PM, Antoni Aloy wrote:
>
> 2009/3/18 Jacob Kaplan-Moss :
> >
> > Hi folks --
> >
> > Quick reminder that Django 1.1 beta is due to drop Friday. This means
> > feature freeze -- any feature additions not completed by the beta
2009/3/18 Jacob Kaplan-Moss :
>
> Hi folks --
>
> Quick reminder that Django 1.1 beta is due to drop Friday. This means
> feature freeze -- any feature additions not completed by the beta
> timeline won't make it into 1.1. Realistically that means that any
> feature addition
On Thu, Mar 19, 2009 at 4:20 PM, Jacob Kaplan-Moss
wrote:
...
>
> /me looks meaningfully at Justin.
FWIW, I've been a terrible contributor on GIS. All praise to Justin's
great work.
--~--~-~--~~~---~--~~
You received this message
On Thu, Mar 19, 2009 at 3:54 PM, Bob Thomas wrote:
> Digging through the (huge) 1.1 milestone list a bit, the following
> seem to be closer to improvements than bugs (IMO). If you have any
> favorites in here, they should probably be looked at for last-minute
>
Digging through the (huge) 1.1 milestone list a bit, the following
seem to be closer to improvements than bugs (IMO). If you have any
favorites in here, they should probably be looked at for last-minute
additions to 1.1 beta, or they may be in danger of missing 1.1
entirely:
Hi folks --
Quick reminder that Django 1.1 beta is due to drop Friday. This means
feature freeze -- any feature additions not completed by the beta
timeline won't make it into 1.1. Realistically that means that any
feature addition not already "close" to done should probably be
tabled.
We've