List of important tasks in the documentation

[Peter Kovacs]

What about adding a page to the library doc that contains a short list of the most important tasks or features that are planed to do in LEMON?

I think, a typical user doesn't browse our tickets to collect the most important plans. That's why I would find it practical to have such a list in the documentation, probably with external links to the corresponding tickets.

[Peter Kovacs]

An attempt for this list:

Port from the 0.x series of LEMON

• Bipartite graph structures (#69)
• Bipartite matching algorithms (#168)
• Floyd-Warshall and Johnson algorithms (#346)
• Prim algorithm (#59)
• Fredman-Tarjan algorithm (#59)
• Edmonds-Karp algorithm (#177)
• Constrained shortest path algorithm (#64)
• Nagamochi-Ibaraki algorithm (#56)
• Steiner tree approximation algorithm (#71)
• LP utilities (#351)

Entirely new features

• Basic multi-threading support (#223, #224)
• Heuristic algorithm for the Maximum Clique problem (#380)
• Algorithms for the symmetric TSP problem
• Binary LGF format (#225)
• A planar graph structure (#363)
• A-star (A*) algorithm (#376)
• Transitive closure algorithm (#378)
• Data structure for line graphs and product graphs (#237)
• MIP solver backend for SCIP (#355)
• LP/MIP solver backend for Gurobi (#367)
• Support arbitrary precision integers and rationals (#343)
• Multicommodity flow algorithms (#296)
• Stable matching (stable marriage) algorithms
• Algorithms for graph and subgraph isomorphism

[Peter Kovacs]

Of course, this list should be maintained sometimes, e.g. before major releases. However, the majority of this work would be the deletion of tasks that have already been done, which would be a pleasure. :)

[Alpar Juttner]

Where do you want to place it? I don't like the idea of putting this kind of info into the repository. On the other hand a page like this on the website is certainly nice to have, provided it is up-to-date. If you take on the duty of maintaining it, then do it.

PS. I think the devel mailing list might be a better place for this kind of discussions, as it is unrelated to the evolution of the actual source code.

[Peter Kovacs]

Replying to alpar:

Where do you want to place it? I don't like the idea of putting this kind of info into the repository. On the other hand a page like this on the website is certainly nice to have, provided it is up-to-date. If you take on the duty of maintaining it, then do it.

Okay, then use the web site for this. As I wrote before, the maintenance wouldn't be a big deal, since this page would be limited to a few major tasks.

PS. I think the devel mailing list might be a better place for this kind of discussions, as it is unrelated to the evolution of the actual source code.

I see.

[Peter Kovacs]

I've created a wiki page for that, see DevelopmentPlans.