Return-Path: <issues-return-124268-archive-asf-public=cust-asf.ponee.io@flink.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 0B29D200CD2
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Thu, 27 Jul 2017 14:11:35 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 0810516AB14; Thu, 27 Jul 2017 12:11:35 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 4DF5B16AB11
	for <archive-asf-public@cust-asf.ponee.io>; Thu, 27 Jul 2017 14:11:34 +0200 (CEST)
Received: (qmail 39744 invoked by uid 500); 27 Jul 2017 12:11:33 -0000
Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@flink.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@flink.apache.org>
List-Post: <mailto:issues@flink.apache.org>
List-Id: <issues.flink.apache.org>
Reply-To: dev@flink.apache.org
Delivered-To: mailing list issues@flink.apache.org
Received: (qmail 39729 invoked by uid 99); 27 Jul 2017 12:11:33 -0000
Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jul 2017 12:11:33 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 0B6841A0A35
	for <issues@flink.apache.org>; Thu, 27 Jul 2017 12:11:33 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -4.021
X-Spam-Level: 
X-Spam-Status: No, score=-4.021 tagged_above=-999 required=6.31
	tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5,
	RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01,
	RP_MATCHES_RCVD=-0.001] autolearn=disabled
Received: from mx1-lw-us.apache.org ([10.40.0.8])
	by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024)
	with ESMTP id YiHtrLAEf6YI for <issues@flink.apache.org>;
	Thu, 27 Jul 2017 12:11:32 +0000 (UTC)
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with SMTP id 11EE95F3D1
	for <issues@flink.incubator.apache.org>; Thu, 27 Jul 2017 12:11:31 +0000 (UTC)
Received: (qmail 39476 invoked by uid 99); 27 Jul 2017 12:11:31 -0000
Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jul 2017 12:11:31 +0000
Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33)
	id 72B78E3823; Thu, 27 Jul 2017 12:11:29 +0000 (UTC)
From: aljoscha <git@git.apache.org>
To: issues@flink.incubator.apache.org
Reply-To: issues@flink.incubator.apache.org
References: <git-pr-4407-flink@git.apache.org>
In-Reply-To: <git-pr-4407-flink@git.apache.org>
Subject: [GitHub] flink pull request #4407: [FLINK-7281] Fix various issues in (Maven) release...
Content-Type: text/plain
Message-Id: <20170727121130.72B78E3823@git1-us-west.apache.org>
Date: Thu, 27 Jul 2017 12:11:29 +0000 (UTC)
archived-at: Thu, 27 Jul 2017 12:11:35 -0000

Github user aljoscha commented on a diff in the pull request:

    https://github.com/apache/flink/pull/4407#discussion_r129824175
  
    --- Diff: pom.xml ---
    @@ -1257,6 +1243,17 @@ under the License.
     		<pluginManagement>
     			<plugins>
     
    +				<plugin>
    +					<groupId>org.apache.maven.plugins</groupId>
    +					<artifactId>maven-release-plugin</artifactId>
    --- End diff --
    
    We were actually not using this before, it was just a leftover in there. It's not even required for our release process, i.e. in the release profile.
    
    However, the plugin can be used to do the stuff that we do in scripts and manually. For example , I can do
    ```
    mvn release:branch \
        -DbranchName=${BRANCH_NAME} \
        -DdevelopmentVersion=${DEVELOPMENT_VERSION}
    ```
    to update the version on master and fork of the branch for a newly released version.
    
    Then I could use
    ```
    mvn release:prepare \
        -Dresume=false \
        -DreleaseVersion=${VERSION} \
        -Dtag=${TAG} \
        -DupdateWorkingCopyVersions=false
    ```
    and
    ```
    mvn release:perform
    ```
    to build the actual release, create the source release, upload the (signed) jars to sonatype and create the release tag.
    
    (I was experimenting with this when preparing for the next release and our release infrastructure is very _interesting_.)
    
    



---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---