On Mon, Jun 16, 2008 at 11:15 AM, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > As requested, I've also added milestones for 1.0 alpha, beta, and > final (as well as a "post-1.0" catch-all). Triagers, feel free to use > these milestones thusly: > > * Any *feature* tickets related to the maybe list get put in the beta > milestone.
One question about this, since I'm probably best positioned to manage the tickets related to file storage. #5361 is already added to the beta milestone, but what should be done about the 15 other tickets that are related to it[1]? Given how much code #5361 already has to move, modify and replace, I've been wrapping some of the fixes up in that one patch (keyword fs-rf-fixed), and the others will be addressed by the documentation (keyword fs-rf-docs). This might be considered hijacking the thread, but I can see three ways to go: * Leave them as they are, and just tell whoever commits #5361 to reference them in the commit message. * Move all of the to the beta milestone, since they are indeed being addressed, and also reference them in the comment message * Close the fixes as duplicates now, and close the doc tickets as wontfix once it lands (which will have to be done regardless). Personally, I'd like to avoid the third option, since I think it's valid to keep them going, as there's not a proper branch to checkout, like newforms-admin has. The difference between the first two is purely bookkeeping though, and I have no preference either way. -Gul [1] http://tinyurl.com/6rxpyp --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
