Re: Some tickets that should perhaps get looked at before 1.1

[Alex Gaynor]

1.1 is not 8 days away, the 1.1 major feature freeze, this means items that
are new features on the 1.1 features list.  1.1 final doesn't ship until
mid-March, which is quite a bit of time considering that starting on
February 15th the only changes that will occur will be bug fixes.

Alex

On Wed, Jan 7, 2009 at 1:56 PM, mrts  wrote:

>
> On Jan 7, 11:56 am, "Alex Gaynor"  wrote:
> > I'd like to remind everyone that the policy for bugs is to fix them, they
> > don't all need to be listed, because the goal is to fix them all.
>
> Let me remind everybody that 1.1 is officially only 8 days away. The
> goal is clearly not achievable in that time :), so a selection has to
> be made. I'd say bringing up trivial, non-controversial, fully
> documented and tested bugfixes like I and Tai Lee did, helps in that
> selection and makes 1.1 a better release. The total ticket mass is
> just unmanageable and picking ripe fruits for the devs to review and
> commit should assist, not hinder in achieving that goal.
>
> ---
>
> Which brings me to a related matter: as there have been no news about
> Honza and his progress on model validation, I'll semi-champion it (at
> least until he pops up again OR a core dev steps up to take it upon
> him/herself OR someone opposes this). I've created a fork of the
> unofficial git mirror for that purpose at
> http://github.com/mrts/django/tree/master
> . Everybody is most welcome to contribute.
>
> By semi-champion I mean that I'll contribute as much as I can beside
> daily job tasks by directly writing code, hanging in #django-dev to
> discuss things with people interested in helping out and merging
> other's patches and upstream changes ASAP. Unfortunately I can not
> warrant that this will be completed it in the short time remaining.
> Design decisions will eventually appear in the wiki:
> http://wiki.github.com/mrts/django
>
> As of now, I've only merged the latest patch by Honza, so the branch
> should be rather unusable (trunk has changed considerably in some
> areas -- neither did the patch apply cleanly nor was it always
> applicable where it did).
> >
>


-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." --Voltaire
"The people's good is the highest law."--Cicero

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@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: Some tickets that should perhaps get looked at before 1.1

[mrts]

On Jan 7, 11:56 am, "Alex Gaynor"  wrote:
> I'd like to remind everyone that the policy for bugs is to fix them, they
> don't all need to be listed, because the goal is to fix them all.

Let me remind everybody that 1.1 is officially only 8 days away. The
goal is clearly not achievable in that time :), so a selection has to
be made. I'd say bringing up trivial, non-controversial, fully
documented and tested bugfixes like I and Tai Lee did, helps in that
selection and makes 1.1 a better release. The total ticket mass is
just unmanageable and picking ripe fruits for the devs to review and
commit should assist, not hinder in achieving that goal.

---

Which brings me to a related matter: as there have been no news about
Honza and his progress on model validation, I'll semi-champion it (at
least until he pops up again OR a core dev steps up to take it upon
him/herself OR someone opposes this). I've created a fork of the
unofficial git mirror for that purpose at 
http://github.com/mrts/django/tree/master
. Everybody is most welcome to contribute.

By semi-champion I mean that I'll contribute as much as I can beside
daily job tasks by directly writing code, hanging in #django-dev to
discuss things with people interested in helping out and merging
other's patches and upstream changes ASAP. Unfortunately I can not
warrant that this will be completed it in the short time remaining.
Design decisions will eventually appear in the wiki: 
http://wiki.github.com/mrts/django

As of now, I've only merged the latest patch by Honza, so the branch
should be rather unusable (trunk has changed considerably in some
areas -- neither did the patch apply cleanly nor was it always
applicable where it did).
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@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: Some tickets that should perhaps get looked at before 1.1

[Alex Gaynor]

I'd like to remind everyone that the policy for bugs is to fix them, they
don't all need to be listed, because the goal is to fix them all.

Alex

On Wed, Jan 7, 2009 at 3:47 AM, Tai Lee  wrote:

>
> I'd also love to see 8898 committed. It looks to be a fairly straight-
> forward bug fix, at least to me.
>
> http://code.djangoproject.com/ticket/8898
>
> Cheers.
> Tai.
>
> >
>


-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." --Voltaire
"The people's good is the highest law."--Cicero

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@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: Some tickets that should perhaps get looked at before 1.1

[Tai Lee]

I'd also love to see 8898 committed. It looks to be a fairly straight-
forward bug fix, at least to me.

http://code.djangoproject.com/ticket/8898

Cheers.
Tai.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@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: Some tickets that should perhaps get looked at before 1.1

[Malcolm Tredinnick]

On Tue, 2009-01-06 at 09:05 -0800, mrts wrote:
> As the list seems to be resuming from holiday hibernation, I risk
> causing another "don't you dare to push us" flame-bombing :) by
> proposing that the following get looked at before 1.1:
> 
> * `__import__(mod, {}, {}, [''])` causes double import of modules [1]

It's already being looked at. It's assigned to me for that reason. As I
mentioned in the last substantive comment on the ticket, solving it has
revealed some other problems with imports that I'm slowly working
through as time permits.

Regards,
Malcolm


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@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
-~--~~~~--~~--~--~---