On the one hand, there's no reason to be protective of the master
branch unless there is some automation that depends on it.
On the other hand, pull requests can wait, and developers can rebase
their pull requests on each other's branches.
Yet another possibility is for a branch to be made for an
+1 for the meeting.
About not merge until the meeting, some of the changes are just simple bug
fixes,
just need review and test.
Gonzalo
On Mon, Jul 13, 2015 at 11:04 AM, Martin Abente <
martin.abente.lah...@gmail.com> wrote:
> If nothing too serious comes up in the following weeks, there might
If nothing too serious comes up in the following weeks, there might be no
need for that release. Regardless of that, we should definitely meet before
start merging changes.
I have sent an invitation email for this Friday.
On Mon, Jul 13, 2015 at 8:37 AM, Gonzalo Odiard
wrote:
> In our schedule
In our schedule [1], we have a possible "Sucrose 0.106.1"
with "exceptional bugfixes tarballs & release" planed.
Can we start to merge changes on master, and later the release manager
can cherry-pick the bugfixes needed for 0.106.1?
I would like to have a development meeting to organize and do so
4 matches
Mail list logo
