[owncloud-devel] Change in backport workflow

Morris Jobke morris at owncloud.com
Sat Jan 31 09:36:42 GMT 2015


Hi,

to keep track of them, we now have the appropriate milestones in place:

6.0.7-next-maintenance
7.0.5-next-maintenance

So please assign these milestones if you add a PR for a backport :)

This helps to keep track of all those changes and reviewers know where 
something will go.

Cheers
Morris

Am 30.01.2015 um 16:25 schrieb Thomas Müller:
> Hi,
>
> I'd like to announce that from now on cherry-picking of fixes to the stable branches are no longer permitted.
>
> Please open pull requests against stable branches and follow the review workflow as it already applies to all pull requests.
>
> Please also add a tag to the subject of the pull request so that we all can easily identify backport pull requests.
> Example: [backport #13740] backport #13740 to stable7 - see https://github.com/owncloud/core/pull/13742
>
> Just in case you are wondering about the reasoning behind this:
> We did introduce regressions due to cherry-picks and with a very high probability we could have spotted them
> with there review process or during the continuous integration executions.
>
> Thanks a lot and take care,
>
>
> Thomas aka DeepDiver
>
>

-- 
Morris Jobke (morris.jobke at owncloud.com)
ownCloud Inc.

Your Data, Your Cloud, Your Way!

ownCloud GmbH, GF: Markus Rex, Holger Dyroff, Frank Karlitschek
Schloßäckerstrasse 26a, 90443 Nürnberg, HRB 28050 (AG Nürnberg)


More information about the Devel mailing list