Meetings/20140408: Difference between revisions
No edit summary |
|||
| Line 31: | Line 31: | ||
Suggestion to move into a mode of cutting a release candidate from develop (when agreed in a meeting), and then holding it in the RC branch until it can be merged to master. This would mean a release process where we don't have to freeze develop at all and can test the RC branch for as long as we want, cherry-picking individual fixes into it. | Suggestion to move into a mode of cutting a release candidate from develop (when agreed in a meeting), and then holding it in the RC branch until it can be merged to master. This would mean a release process where we don't have to freeze develop at all and can test the RC branch for as long as we want, cherry-picking individual fixes into it. | ||
=== Communication through Diaspora HQ === | |||
What kind of communication do we want through Diaspora HQ? Do we need more formal guidelines? | |||
== What did we decide? == | == What did we decide? == | ||
== IRC Logs == | == IRC Logs == | ||
Revision as of 19:36, 7 April 2014
Time and date
Tuesday 8 April 2014, 7.30 PM UTC. #diaspora-meeting @ FreeNode.
Topics to discuss
FSSN
We have to talk about it.
Official list of pods
It would be nice to have an official list of pods, fusion of podutime and the stats hub of Jason, on diasporafoundation.org. Who wants to work on that? Do we want it directly inside the website or in a subdomain? Which technology do we want to use?
Changelog for the develop branch
It happened several times that a commit in the develop branch causes a regression, which is fixed in the develop branch before we release a new version. Should we add a changelog line about these kind of fix? People upgrading the stable branch don't need to know, it's only for people running the develop branch. Maybe a special section, which will be removed during the release process?
FISL conference, May
Apparently there is going to be a Diaspora booth at this free software conference. See a comment on https://joindiaspora.com/posts/3813341 for more details.
Questions: what shall we do in order to participate, and how should we do this?
Community blogs
We still have the 'Planet' referred to in various places (for example, the wiki) but it has never been set up. Is this something that we still desire, and if so how should we go about setting it up?
Release process
Suggestion to move into a mode of cutting a release candidate from develop (when agreed in a meeting), and then holding it in the RC branch until it can be merged to master. This would mean a release process where we don't have to freeze develop at all and can test the RC branch for as long as we want, cherry-picking individual fixes into it.
Communication through Diaspora HQ
What kind of communication do we want through Diaspora HQ? Do we need more formal guidelines?