A bit late, but here's my update to GSoC-1 (admin-ui). My branch is in good
shape, but tests are sparse and docs are nonexistant. Two more weeks is
enough time for me to get the following done:
1) Moar tests
2) Merge with trunk
3) Split out each feature into individual patches and throw them
Since it appears there are some people who have code ready but have
time constraints due to holidays, I'm going to (by release-manager
fiat, unless Adrian or Jacob want something else) plan 1.2 alpha (and
corresponding major feature freeze) for Tuesday, January 5. Any major
feature not in trunk by
On Wed, Dec 23, 2009 at 2:34 AM, James Bennett wrote:
> Technically, the major feature freeze for Django 1.2 was to have
> happened sometime yesterday, US Central time. As of this moment, we're
> not actually frozen, but will be as soon as I hear status reports on
> the
C-6 (test
> improvements). Unfortunately I have not had time to devote to moving that
> along, and so far as I know nobody else has either -- I have not seen any
> activity or patches or discussion that would indicate anyone was hoping to
> get something done on it for the 1.2 feature freeze
something done on it for the 1.2 feature freeze. So at this point I
think it will have to wait for 1.3. (If I'm wrong and there is someone out
there hoping to get something in by yesterday, please speak up...but I'm not
going to have any time to look at anything related to it for at least a
week, so unless
On Dec 23, 8:34 am, James Bennett wrote:
> * URLs-1 (get_absolute_url replacement)
The code's not ready - I have the get_url / get_url_path methods but I
don't have a good enough hold yet on what actually needs to be done to
replace the existing get_absolute_url behaviour
Technically, the major feature freeze for Django 1.2 was to have
happened sometime yesterday, US Central time. As of this moment, we're
not actually frozen, but will be as soon as I hear status reports on
the following (high-priority features which have not yet listed a
commit on the 1.2 features