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
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
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. If there has been
ed 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.com/django/deps/blob/master/final/0001-dep-process.rst#dep-types> > is > the way to go to
a move just for the >>> increase in engagement. >>> >>> Carlton, Mariusz, how would you gauge the level of triage activity in >>> Trac from non-core members? High/Medium/Low? >>> >>> https://github.blog/changelog/2019-05-23-triage-and-maintain-
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?