> As with many things, the process of becoming a committer is documented
> in our contributing document
> (http://www.djangoproject.com/documentation/contributing/#commit-access
> ):
>
> [...]
>
> To request commit access, please contact an existing committer
> privately. Public requests for comm
On Thu, Jul 3, 2008 at 9:26 AM, Jannis Leidel <[EMAIL PROTECTED]> wrote:
> Just out of curiosity, could we fix that bottleneck by appointing more
> developers to be core developers?
As with many things, the process of becoming a committer is documented
in our contributing document
(http://www.dja
On Thu, Jul 3, 2008 at 9:26 AM, Jannis Leidel <[EMAIL PROTECTED]> wrote:
>> Even if these sorts of features have a patch and are "Ready for checkin,"
>> that does not mean they get a 1.0 milestone. They still take core
>> developer time to review and commit, time that also needs to be
>> focused
> I would like to stress the point that features not on the list are not
> to be put in any 1.0 milestone. For those working on tickets for
> features or enhancements that are not on the list, please understand
> that these are lower priority than vetted features and *all* bugs. If
> you really
I would like to remind those out there setting milestones on tickets to
follow the following guidelines that Jacob put forth:
* Must-have feature bugs go in the "1.0 alpha" milestone. These
basically should be all nfa-blocker tickets. Bugs in the must-have
features are not to be part of thi
