Differences between revisions 62 and 64 (spanning 2 versions)
Revision 62 as of 2018-06-04 14:49:13
Size: 4901
Editor: MalteHelmert
Comment: Reviews of issue668 done.
Revision 64 as of 2018-06-05 14:29:44
Size: 5244
Editor: JendrikSeipp
Comment: remove conditional effect issue
Deletions are marked like this. Additions are marked like this.
Line 40: Line 40:
 * http://issues.fast-downward.org/issue397: new semantics for conditional effects (code review, Jendrik)
Line 47: Line 46:
 * http://issues.fast-downward.org/issue791: Use task interface for StateRegistry (code review, Florian)
 * http://issues.fast-downward.org/issue792: Get rid of g_successor_generator (code review, Florian)
 * http://issues.fast-downward.org/issue793: Introduce/collect utility methods for printing proxy objects (code review, Florian)
 * http://issues.fast-downward.org/issue794: Reduce code duplication in axiom evaluator (code review, Florian)

Review queue

Why a queue and how to use it?

  • The queue is intended as a TODO list for Malte. We hope that it can be a useful tool for Malte to keep track of who wants want and to keep the waiting times reasonably fair.
  • Use the queue for code reviews, discussions and other Fast Downward things that Malte should work on.
  • As of now, the queue is intended to be used by the Basel AI group only. If you think this should be changed, please get in touch.
  • Add new items to the end of the queue. Usually, Malte will work from the front of the queue, but there may be reasons to promote/demote things.
  • There is no need to put everything into the queue. It is intended for things that you would ideally like to get done right now, but that are not terribly urgent.

  • The queue should be easy to use and useful for everyone involved. If it turns out that this is not the case, we should get rid of it again.

The queue

FastDownward: ForDevelopers/ReviewQueue (last edited 2023-07-28 09:55:50 by MalteHelmert)