Meetings/20160829: Difference between revisions
(0.7 Milestone) |
(grammar) |
||
| Line 8: | Line 8: | ||
We usually assign a milestone to an issue only when we solve it, to avoid doing fake promise we can fail to achieve. | We usually assign a milestone to an issue only when we solve it, to avoid doing fake promise we can fail to achieve. | ||
However, we can still discuss what we want to focus for the next major release. Those | However, we can still discuss what we want to focus for the next major release. Those issues could then be push forward for example with bounties on bountysource. | ||
Suggestions: | Suggestions: | ||
Revision as of 14:22, 18 August 2016
Time and date
Monday the 22nd of August 2016, 7 PM UTC. #diaspora-meeting @ FreeNode.
Topics to discuss
0.7.0.0 milestone
We usually assign a milestone to an issue only when we solve it, to avoid doing fake promise we can fail to achieve. However, we can still discuss what we want to focus for the next major release. Those issues could then be push forward for example with bounties on bountysource.
Suggestions:
- Being able to mention using the mobile version