[jira] [Comment Edited] (REEF-498) Create scripts for release versioning, packaging, checksum

["Markus Weimer (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/REEF-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651997#comment-14651997 ] 

Markus Weimer edited comment on REEF-498 at 8/3/15 3:39 PM:
------------------------------------------------------------

Let's collect the set of files that need version changes here for future reference:

  * In {{/pom.xml}}, we need to update the version of the project as a whole.
  * In all the sub-modules, we need to update the {{pom.xml}} of the parent POM.
  * For all C# projects, we need to update the {{AssemblyInfo.cs}} file with the new version.
  * For the release, the NuGet version needs to be changed *not* to end in {{SNAPSHOT-###}}. For the post-release {{master}} branch, that needs to be reverted.

Some things I am a bit more fuzzy on:

  * Do we need to do anything with the website? Can we do some of those things in an automated fashion?
  * How is the versioning for the C++ DLL handled? [~beysims], can you advise?
  * We need to do *something* about the DLL signing. When we make a *binary* release, those artifacts need to be signed with a *private* private key, and not the *public* private key we use during development. [~juliaw], can you advise?



was (Author: markus.weimer):
Let's collect the set of files that need version changes here for future reference:

  * In `/pom.xml`, we need to update the version of the project as a whole.
  * In all the sub-modules, we need to update the `pom.xml` of the parent POM.
  * For all C# projects, we need to update the `AssemblyInfo.cs` file with the new version.
  * For the release, the NuGet version needs to be changed *not* to end in `-SNAPSHOT-###`. For the post-release `master` branch, that needs to be reverted.

Some things I am a bit more fuzzy on:

  * Do we need to do anything with the website? Can we do some of those things in an automated fashion?
  * How is the versioning for the C++ DLL handled? [~beysims], can you advise?
  * We need to do *something* about the DLL signing. When we make a *binary* release, those artifacts need to be signed with a *private* private key, and not the *public* private key we use during development. [~juliaw], can you advise?


> Create scripts for release versioning, packaging, checksum
> ----------------------------------------------------------
>
>                 Key: REEF-498
>                 URL: https://issues.apache.org/jira/browse/REEF-498
>             Project: REEF
>          Issue Type: Improvement
>            Reporter: Brian Cho
>            Assignee: Dongjun Lee
>
> Scripts for release versioning, packaging (with the correct RC version), and creating checksums will make the release manager's life much easier.
> [~dongjun] has kindly volunteered to create the scripts. As 0.12 release manager, I'd like to give these scripts a test run. My proposal is that we create a PR for the scripts soon, with the aim of using and reviewing them during the 0.12 release process, and then merging the battle-tested script *after* the 0.12 release.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)