Re: 1.2 Feature freeze

[Zain Memon]

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 in trac
4) Docs for each feature

Thanks a lot for pushing the date.

Regards,
Zain

On Wed, Dec 23, 2009 at 12: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 following (high-priority features which have not yet listed a
> commit on the 1.2 features page):
>
> * GSoC-1 (admin UI)
> * CSoC-2 (WSGI improvements)
> * GSoC-4 (model validation)
> * GSoC-6 (test improvements)
> * Templates-4 (tag loading improvements)
> * URLs-1 (get_absolute_url replacement)
> * Views-1 (class-based generic views)
>
> If you're one of the people involved with one of the above features,
> you need to get me a status update as soon as humanly possible,
> preferably in one of two forms:
>
> 1. "The code's ready and I'll check it in as soon as I finish writing
> this email to you", or
> 2. "The code's not ready, guess it'll wait for 1.3"
>
> If the status update consists of "it's checked in but nobody updated
> the 1.2 features page", you will be slapped with a large trout.
>
> (in case y'all can't tell, I have no plans to let 1.2 slip like 1.1 did...)
>
>
> --
> "Bureaucrat Conrad, you are technically correct -- the best kind of
> correct."
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-develop...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>
>

--

You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: 1.2 Feature freeze

[James Bennett]

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 then doesn't make 1.2.


-- 
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."

--

You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: 1.2 Feature freeze

[Joseph Kocherhans]

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 following (high-priority features which have not yet listed a
> commit on the 1.2 features page):
>

[snip]

> * GSoC-4 (model validation)

I'd like to get this in. I have a current diff on my laptop that I'm
going to review again on the plane this afternoon, but I don't think
there's any development work that it needs. Merging the changes from
multidb into the branch might take some effort, but I think Honza is
willing to do that if we commit the branch to trunk.

I'm going to have questionable internet connectivity until Monday, but
if I can get online I'd like to check this in in the next couple of
days. (I will have access to email on my phone though, so I'll watch
this thread.) I don't want to break the schedule, but it'd be a shame
to let this slip to 1.3.

Joseph

--

You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: 1.2 Feature freeze

[Honza Král]

Hi everybody,

model-validation patch hasn't changed since September (except merges
with trunk) basically, there is one outstanding issue (#12078) that I
can fix over the holidays. Also a merge with current trunk needs to be
done because of the huge changes in the past few days.


I have both time and resources to get the patch the next day or two,
what I don't have is:

* ANY feedback on the actual code. Is the code ok? What is missing?
What should I change?

* commit bit so I need somebody to work with me here. Joseph has been
busy it seems.


Will somebody please step up and tell me what I have to work on to get
it committed or, better yet, do the actual commit?

Thanks!



Honza Král
E-Mail: honza.k...@gmail.com
Phone:  +420 606 678585



On Wed, Dec 23, 2009 at 2:33 PM, Karen Tracey  wrote:
> I'm listed as one of the interested committers on GSoC-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.  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 there's another committer who can help with it, I think it's
> too late for it to make 1.2.)
>
> Karen
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-develop...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>

--

You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: 1.2 Feature freeze

[Karen Tracey]

I'm listed as one of the interested committers on GSoC-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.  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 there's another committer who can help with it, I think it's
too late for it to make 1.2.)

Karen

--

You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: 1.2 Feature freeze

[Simon Willison]

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 and all of it's
idiosyncrasies.

Cheers,

Simon

--

You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.