Re: Status of 4.1 pre-release.

[thinkwel...@gmail.com]

Will the psycopg3 backend  
land in time for the 4.1 release?  I'm looking forward to it, as it should 
support PyPy much better than psycopg2 does.

On Wednesday, May 11, 2022 at 3:33:56 AM UTC-4 carlton...@gmail.com wrote:

> Hi Jacob. 
>
> I've always taken it that the person reviewing will do the marking. (I.e. 
> I don't read it as saying, "Find someone to review it and then mark it RFC 
> yourself", which would contradict the note in the FAQ yes.) 
>
> #32559 is on my list. IIRC it was there bar a few last tweaks, so I wanted 
> (want) to get it resolved. 
> C.
>
> On Wed, 11 May 2022 at 09:04, Jacob Rief  wrote:
>
>> Hi Carlton,
>> there is somehow a contradiction:
>> In https://code.djangoproject.com/wiki/Version4.1Roadmap it's written:
>>
>> Better yet, find someone to review your patch and mark the ticket as 
>>> "Ready for checkin".
>>>
>>
>> but 
>> https://docs.djangoproject.com/en/4.0/faq/contributing/#i-m-sure-my-ticket-is-absolutely-100-perfect-can-i-mark-it-as-ready-for-checkin-myself
>> states:
>>  
>>
>>> ’m sure my ticket is absolutely 100% perfect, can I mark it as “Ready 
>>> For Checkin” myself?
>>>
>>> Sorry, no. It’s always better to get another set of eyes on a ticket. If 
>>> you’re having trouble getting that second set of eyes, see questions above.
>>>
>>  
>> I'm actually asking, because of this I left one of my tickets 
>>  on "Accepted".
>>
>> Kind Regards,
>> Jacob
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django developers (Contributions to Django itself)" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-develop...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-developers/b4e386d5-b8be-4880-aa29-0c923c986518n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/2b204160-31f2-46d2-9602-08a9445146e1n%40googlegroups.com.

Re: Status of 4.1 pre-release.

[thinkwel...@gmail.com]

> Next step would be someone to pick the preliminary work up and push it 
forward.

I guess I thought the "preliminary work" was already done. There's a driver 
written, and a PR for a django backend.

I'd asked [Daniel 
Varrazzo](https://github.com/dvarrazzo/django-psycopg3-backend/issues/6) if 
he was planning to do it, and he said:

> I am not actively working with the Django developers: I wrote the driver 
and the first iteration of the backend but I left the ball in their field. 
I give them feedback when they ask, but I'm not doing more than this. 

> You should hear from the Django project about their plans.
On Wednesday, May 11, 2022 at 8:04:20 AM UTC-4 carlton...@gmail.com wrote:

> On Wed, 11 May 2022 at 13:53, thinkwel...@gmail.com  
> wrote:
>
>> Will the psycopg3 backend <https://code.djangoproject.com/ticket/33308> 
>> land in time for the 4.1 release?  I'm looking forward to it, as it should 
>> support PyPy much better than psycopg2 does.
>>
>
> No. It's not been worked on recently as far as I know. Next step would be 
> someone to pick the preliminary work up and push it forward. (A major 
> feature like that isn't something we'd add to the roster the week before 
> the feature freeze: we'd likely see it coming the whole release cycle.) 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/f4d15ee7-faee-4841-8518-970ab6a2c1a7n%40googlegroups.com.

Re: Status of 4.0 release blockers.

[thinkwel...@gmail.com]

Will it be possible to get ticket 32948 
 closed and included in 4.0? 
I'd be super-glad if that could happen.

On Monday, September 13, 2021 at 1:04:59 AM UTC-4 Mariusz Felisiak wrote:

> Hi y'all,
>
> Time to begin release process for the next major release, Django 4.0!
>
> The 4.0 feature freeze is scheduled (according to 
> https://code.djangoproject.com/wiki/Version4.0Roadmap) for September 20. 
> We'll probably release the alpha a few days later.
>
> We have a few larger patches we want to finish reviewing:
>
> https://github.com/django/django/pull/14437 - Fixed #33012 -- Added Redis 
> cache backend.
> https://github.com/django/django/pull/14846 - Fixed #32873 -- Deprecated 
> settings.USE_L10N.
> https://github.com/django/django/pull/13733 - Fixed #27674 -- Deprecated 
> GeoModelAdmin and OSMGeoAdmin.
> https://github.com/django/django/pull/14819 - Fixed #31026 -- Switched 
> form rendering to template engine.
> https://github.com/django/django/pull/14848 - Fixed #32365 -- Made 
> zoneinfo the default timezone implementation.
>
> Best,
> Mariusz 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/a3976277-c1f1-4028-ae47-51329eb7d2abn%40googlegroups.com.