I've started addressing some of the other things you mentioned by moving things to later milestones or making them 0.6 blockers. I think the 'blocker' tag is more semantic than meaningful (everything under 0.6 should theoretically be done for a release, regardless of priority), so please don't immediately assume anything not marked as a blocker shouldn't be looked at.
What are your reasons for wanting translation to be moved to a later release? There are more non-english-speaking Habari users than we realize, I would think making sure things can be translated properly would be a big issue. And things like #456 should be easy to take care of, if not fix. As suggested, it could just be hidden until it works... It's a little thing, but it would make Habari seem much less "quirky" or "broken" if it were taken care of before release. I wouldn't call it a "blocker", but that doesn't mean someone shouldn't take a minute or two to look at it. As for autop(), I'd like to hear other opinions on that... Personally, I'm all in favor of "fixing" autop sooner rather than later, but I haven't played with the branch to know whether or not it would cause more problems than it would fix at this point. Maybe Sean could comment? Tickets like #537 I'm inclined to leave set for 0.6 because they could be a very easy fix - for someone who knows wtf they're doing in that mass of regex. If someone who knows enough about regex to feel comfortable looking at that would care to either fix it or push it off, that would be great. In general we just need to look at the tickets and see whether or not they're worthy of waiting for. Just because it's not a "blocker" doesn't mean it shouldn't be addressed before 0.6. Polish is just as important as actual working-ness if the UI is too quirky or annoying to use. On Mon, Mar 23, 2009 at 6:12 AM, Michael Harris <[email protected]>wrote: > > 2009/3/23 Chris Meller <[email protected]>: > > FYI, there are 42 tickets with a 0.6 milestone still open on Trac: > > http://trac.habariproject.org/habari/report/3 > > Another release comes around and we still, unfortunately, don't have a > proper strategy for dealing with milestones. At this stage, I think we > need to identify how many of those tickets are blockers for 0.6. My > guess is very, very few. > > Some of them are catchall bugs that probably should be closed anyway, > like #11 and #26, and more specific bugs opened if necessary. > > And some are done, I think, such as #372 and #886. > > IMHO, these should obviously be moved to a later release: > * Anything to do with autop (#767, #862) because the autop branch will > fix them later > * Admin tag management (#602, there are already related tickets with > later milestones) > * subsites (#61, which was slated for 0.8 anyway) > * translation (#893, #864, #915, #874, #744) > * Quick upload for silos (#456) > > This is just from a quick look. I'm sure there are others that don't > _need_ to go into 0.6. > > -- > Michael C. Harris, School of CS&IT, RMIT University > http://twofishcreative.com/michael/blog > IRC: michaeltwofish #habari > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
