Would it be possible to expand the scope of the recently accepted secret
key rotation ticket to include the ability to live rotate other credentials
as well, such as the DB credentials?
Or would this be a separate thing all together?
https://groups.google.com/forum/#!searchin/django-developers
worth familiarising oneself with prior art.
>>>
>>> For what it's worth I'd strongly support such a move just for the
>>> increase in engagement.
>>>
>>> Carlton, Mariusz, how would you gauge the level of triage activity in
>>> Trac fr
ject.com/tree/master/svntogit
>
> It would be nice to preserve these links in issues copied from Trac to
> GitHub, which probably means pre-processing comments to rewrite links.
>
> There may be more, but that's what comes to mind!
>
> A process DEP
> <https://github.
o-developers/aiyE__qSHBY/discussion
https://groups.google.com/d/msg/django-developers/5CVsR9FSqmg/qKD3QCrLCAAJ
On Tuesday, August 6, 2019 at 11:24:45 PM UTC-7, John Gooding wrote:
>
> I'd like to propose moving Django issues to github and make a real
> decision on it here in this thread.
I'd like to propose moving Django issues to github and make a real decision
on it here in this thread. If there has been a recent discussion on this I
apologize, but searching for issue tracking / github links to about every
thread ever posted here.
I believe this would lower the barrier to ent
To be clear, I am not saying there is a bug. It does what it is programmed
to do. I am saying the expected behavior of the API / CLI / whatever you
want to call it is inconsistent.
I am not going to get into an argument of what a "proper" django structure
is, etc. I want to focus purely on the
