Hi list, We have taken the habit to use the github pull request interface to share code and have discussion a long time before a merge happens. The web interface is indeed great and helps people pitching in and reviewing code. However, it clutters the PR list: I am having a hard time prioritizing reviews and merge, and I worry a lot that some ready-to-merge work is being lost.
I suggest that we use the following conventions: * PRs that are not ready to be merged should be named 'WIP: ...' (for 'Work In Progress') * PRs that are ready to be merged, or more accurately, for which the contributors feel that they are ready to be merged, should be renamed to 'MRG: ...' It is easy to rename PRs, so we can do always update those labels as we go. What do people think about this suggestion? If people agree, I'll add it to the develop docs. Gael ------------------------------------------------------------------------------ Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _______________________________________________ Scikit-learn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
