Hi Reinout, > I'm pretty sure that "beta" means "nope, you won't get any changes that > aren't bug fixes in", but I cannot find the page that says that. I assume I'm > right?
That's true. > Related, a suggestion for the next release cycle: send an email to the > mailinglist that there's a beta coming up and that you ought to hurry up to > get new features in. I sort of did, just after the alpha: https://groups.google.com/group/django-developers/browse_thread/thread/74eff3def6ef47af?pli=1 > So... tickets with patches. I'm waiting patiently. I obviously shouldn't have > done that, I guess :-) But I also didn't know when the beta would be out. And > I also didn't want to bug the mailinglist unnecessary. So I guess I should > not have assumed such a small patch would get in no problem. > > Question is, how can I know next time? Some keyword on the ticket that I can > look for? Am I allowed to bug the mailinglist? Both tickets currently are in the list of tickets that need a review. Since you aren't the author of the patches, you're welcome to review them. If you think they match all the criteria for inclusion in Django, mark the tickets as ready for checkin. (See item 3 in the email I linked to above for more.) Finally, you can join the #django-dev IRC channel on FreeNode if you have questions and don't want to bug the mailing-list. Best regards, -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
