Hi
Don't like to hassle, but I'm increasingly wondering what the plan is
for the many new features due to be included in django. I think this
entails these branches:
full-history
multiple-db-support
per-object-permissions
schema-evolution
search-api
sqlalchemy
generic-auth (?)
I'd really like t
On 10/31/06 11:18 AM, Joeboy wrote:
> Don't like to hassle, but I'm increasingly wondering what the plan is
> for the many new features due to be included in django. I think this
> entails these branches:
This comes up every few weeks.
We're really still waiting on end-user testing on the SoC br
On 10/31/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> This comes up every few weeks.
>
I've wikified this response here:
http://code.djangoproject.com/wiki/ActiveBranches
I linked to any branch detail pages I could find, relevant groups
discussions, and added a suggestion to test one of the
I think it would be a good idea to have a bug-squash/testing day on IRC
for certain branches. Maybe the developers of those branches let
someone (?) know they'd like some testing. A day is picked and that's
the testing day. Try to raise awareness on the mailing lists and that
IRC will be the pl
Regarding the, apparent, less than optimal participation, I think it
might help to dedicate a section on the Django homepage to development
in general or these branches in particular. It's a bit difficult to
find out what needs to be done, it is only posted on this google
discussion group, and aft
I've reported at least a few times on django-dev and django-users that
I've had a lot of success with row-level-permissions. I found some
bugs early on, but Chris Long squashed them all for me. I'm currently
running a production site with that branch.
My requirements of it are pretty minimal, but