Re: [Planner Dev] Re: Roadmap



Jani Tiainen wrote:
Richard Hult wrote:

Richard Martin wrote:

Hi,

I was just wondering if there is a roadmap for planner?



Hi,

Not really, currently. We have a list of tasks to finish for the next few releases that we keep in bugzilla:

0.13:

http://bugzilla.gnome.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=planner&target_milestone=0.13&long_desc_type=allwordssubstr&long_desc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&namedcmd=clsdaniel&newqueryname=&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=

0.14:
http://bugzilla.gnome.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=planner&target_milestone=0.14&long_desc_type=allwordssubstr&long_desc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&namedcmd=clsdaniel&newqueryname=&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=



There is currently a lack of resources though so the project is a bit stalled at the moment.


Well, let's give a hand, I've started to investigate and fix bugs marked for 0.13 release. I'm just concentrating on bugs in code, I don't fix documentation bugs (151485 and 151603), that's for someone else's job.. =)

Short summary:

Bug 140536: Critical path broken

Not started.

Bug 154253: Milestones shouldn't be able to have subtasks

Partly fixed. There is still might be possible to load file that has faulty subtasks. (not tested tough).

Under work:
Bug 151730: Toolbar buttons unavailable after indenting a task

There is nasty feature in indent functions. When you indent items in tree, it destroys selection (selects only first selected item) and blocks selection change signal.

You can consider this one as fixed. Only thing is that indent/undent works in a pretty unpredictable way when you have multiple tasks selected that are not grouped together. That should be fixed definitely in the future.

And command states should be fixed also to reflect what you see. Now you have most of buttons enabled even you can't do eg. unindent...

Bug 154507: Test database upgrade/creation code

Since there is no reports, I can also run tests and check that it goes allright. Maybe it could be closed...





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]