freemarker-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jacopoc <>
Subject [GitHub] incubator-freemarker-site pull request #2: Miscellaneous edits, mostly to th...
Date Thu, 05 Jan 2017 07:07:54 GMT
GitHub user jacopoc opened a pull request:

    Miscellaneous edits, mostly to the new "committer how-to" document.


You can merge this pull request into a Git repository by running:

    $ git pull misc-edits

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2
commit d2d3c4e062692d7e7c480e088a62bb700bd030ec
Author: Jacopo Cappellato <>
Date:   2017-01-05T06:24:21Z

    Fix for typo.

commit 171564660a9a54456ba37a98a205e8cb2dc02470
Author: Jacopo Cappellato <>
Date:   2017-01-05T06:36:51Z

    Replaced "dispute" with "discussion": the latter better describes
    what usually happens during a commit review by the community.

commit 699553d36946ad87bc512d138831aa2cc9652362
Author: Jacopo Cappellato <>
Date:   2017-01-05T06:41:20Z

    Fix for typo.

commit 2024fc5b002108eff2f6d155a31158c40d79064a
Author: Jacopo Cappellato <>
Date:   2017-01-05T06:48:34Z

    Replaced "release engineer" with "release manager" because the latter is
    the term used in other ASF resources:
    Also slightly modified the sentence to avoid the usage of the verb
    "appointed" that may imply the presence of a hierarchy, which is not
    the case.

commit 98d6eb9ed23b33a36178c44eaba6da8a11956baf
Author: Jacopo Cappellato <>
Date:   2017-01-05T07:03:13Z

    Modified the way "source" and "binary" releases are described to be
    compliant with the description of a "valid release" for the ASF:


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message