I've posted the final Django 1.0 roadmap, incorporating all great
feedback I got here:
http://code.djangoproject.com/wiki/VersionOneRoadmap
I've also updated the features page
(http://code.djangoproject.com/wiki/VersionOneFeatures) to reflect the
new list and to have a list of committers/lieutenants. If anyone wants
to volunteer to fill the "???" slots, let me know.
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:
* Must-have feature bugs go in the "alpha" milestone. These basically
should be all nfa-blocker tickets. *Bugs* in the must-have features
are *not* to be part of this milestone; they can be fixed after the
alpha.
* Any *feature* tickets related to the maybe list get put in the beta milestone.
* Remaining *bugs* go in the 1.0 final release.
Jacob
Hi folks --
I've posted the final Django 1.0 roadmap, incorporating all great
feedback I got here:
http://code.djangoproject.com/wiki/VersionOneRoadmap
I'd like to merge it about a week before the sprint. (Hopefully I can
free up some time soon to help make that happen.) I think that would
give the sprinters a whole lot more to do. Most of the existing nfa
stuff is non-trivial right now, but I'd imagine there will be some
easier bugs discovered once more eyeballs are on the code.
Joseph
BTW, I've also added a batch-modify plugin to Trac so that we can
easily update lots of tickets at once. Email me privately or find me
on #django-dev if you'd like access to the feature.
Jacob
Hopefully my question makes sense (it is a Monday after all)
Thanks!
Jeff Anderson
ps:
Some examples:
http://code.djangoproject.com/ticket/7179
http://code.djangoproject.com/ticket/7361
http://code.djangoproject.com/ticket/6077
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
Do both of these, and also tag with with a common tag (see, e.g., the
qsrf-fixed or nfa-fixed tag). I'd suggest "fstorage-fixed" or
something. Actually, if you tag them first it's easy to move them all
to the milestone -- I'd like the milestones to reflect the actually
ticket count (even for dups of this nature).
Jacob
It's going to be a close call either way for any of these types of
tickets. I think we'll lean towards "no" if there's not an actual bug,
but mark them in the 1.0 milestone anyway - we can always defer 'em
later on.
What we *don't* want to do is get caught trying to fix these things
before the merge; stuff like this is OK to postpone.
Jacob
Tags were already done, but I've now moved them all into the beta
milestone as well. I hope I didn't overstep my boundaries here, but I
also added a note on the VersionOneRoadmap to explain the related
tickets and how the tags should be used.
-Gul