In my opinion, it may be too soon to make an evaluation of DEP.
Most importantly, it has to be put in context to what happened/is
happening:
- there was a security release
- there was a fix to the security release
- there is a version of Django to be released with *considerable* new
features, that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/29/2014 08:58 PM, Michael Manfre wrote:
> From DEP 001:
>
> "Once you've written a DEP and submitted the pull request, post a
> message about it to the django-developers mailing list. At that point,
> Django developers will make sure it's techni
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adding my two cents below regarding DEPs.
On 05/08/2014 05:49 AM, Łukasz Rekucki wrote:
> Discussing DEPs on Github inside Pull Request comments seems like a
> really bad idea, because it excludes a whole bunch of people that are
> subscribed to this
Hi Jannis,
On Fri, May 9, 2014 at 3:11 AM, Jannis Leidel wrote:
> Michael,
>
> First, I would appreciate if you'd give feedback in a less passive
> aggressive style. I hope it's just a matter of language barrier but your
> mail came over as far too demanding for just a "curious" question.
>
I
Aymeric,
On 08.05.14 19:23, Aymeric Augustin wrote:
> On 8 mai 2014, at 16:26, Michael Manfre wrote:
>
>> It's been almost a month and the next step in the process for the first two
>> DEPs is to merge the PRs and assign numbers to make them "active". The
>> discussion for each of them can tak
Michael,
First, I would appreciate if you'd give feedback in a less passive
aggressive style. I hope it's just a matter of language barrier but your
mail came over as far too demanding for just a "curious" question.
As far as I can see there has been activity in the pull requests
(including from
On 8 mai 2014, at 16:26, Michael Manfre wrote:
> It's been almost a month and the next step in the process for the first two
> DEPs is to merge the PRs and assign numbers to make them "active". The
> discussion for each of them can take place over the coming months. I hate to
> sound so cynica
Their is some value in commenting directly on a pull-request, for example
you can comment on specific lines of code, and the interface is very
friendly.
With that being said, having a link to related google group pages (or
another mail-archive site) in the pull-request message would be a great
It's been almost a month and the next step in the process for the first two
DEPs is to merge the PRs and assign numbers to make them "active". The
discussion for each of them can take place over the coming months. I hate
to sound so cynical, but if none of the 30+ current core developers are
able t
I have to agree that the decentralized nature of the mailing list would
probably stand the test of time a bit better, plus the ability to in-line
reply makes larger discussions easier on the eyes.
In reference to OPs original comments;
Enhancement proposals are a great idea, but ultimately they wi
Hi folks,
Discussing DEPs on Github inside Pull Request comments seems like a
really bad idea, because it excludes a whole bunch of people that are
subscribed to this list (I always thought this was the sole purpose of
this list).
The best thing about PEPs is that they always get posted to python
Hi,
On Thursday, May 8, 2014 2:13:52 PM UTC+2, Carl wrote:
>
> Just noticed this message, and the DEP PRs are still open a week later.
> Can someone shuffle this along, please?
>
We are in the final stages of 1.7, I personally would rather focus on that
first.
--
You received this message
Hi all,
> If no-one else has looked at and commented on those two DEPs within
> the next day or two, I will have time to do so, and will do so (and
> feel free to poke me if I haven't).
Just noticed this message, and the DEP PRs are still open a week later.
Can someone shuffle this along, please
It's worth noting that during that two-week time period the core team has
been a bit preoccupied with doing a security release and followup bugfix
release :)
If no-one else has looked at and commented on those two DEPs within the
next day or two, I will have time to do so, and will do so (and feel
>From DEP 001:
"Once you've written a DEP and submitted the pull request, post a message
about it to the django-developers mailing list. At that point, Django
developers will make sure it's technically feasible, not spam, etc., assign
it a DEP number and commit it to the repository as "Active." Th
15 matches
Mail list logo
