Re: Towards Apache Apex 3.6.0 release

--> > The remote 3.6.0 branch stays at 3.6.0-SNAPSHOT until release is complete. > > The tag has the release version. > > > > > There is no step to push release branch to remote while being at > 3.6.0-SNAPSHOT. Is this step missing from release document? > > Earlier, it would have been sufficient

Re: Towards Apache Apex 3.6.0 release

On Sat, Apr 29, 2017 at 2:16 AM, Thomas Weise wrote: > The remote 3.6.0 branch stays at 3.6.0-SNAPSHOT until release is complete. > The tag has the release version. > > There is no step to push release branch to remote while being at 3.6.0-SNAPSHOT. Is this step missing from

Re: Towards Apache Apex 3.6.0 release

The remote 3.6.0 branch stays at 3.6.0-SNAPSHOT until release is complete. The tag has the release version. Your local branch obviously needs to be same as you create the tag from it. Perhaps we need to word this differently in the instructions. Thomas On Fri, Apr 28, 2017 at 12:57 PM, Tushar

Re: Towards Apache Apex 3.6.0 release

I am executing following command to prepare an RC for ApexCore 3.6.0. git checkout -b release-3.6 master git checkout master dv=3.6.0-SNAPSHOT rv=3.7.0-SNAPSHOT for a in `git grep -l "${dv}"`; do echo $a; sed -i 's/'"${dv}"'/'"${rv}"'/g' $a; done git commit --author "Apex Dev

Re: Towards Apache Apex 3.6.0 release

All the issues marked as 3.6 have been resolved. I will go ahead and prepare RC1 candidate. Thanks, - Tushar. On Wed, Apr 26, 2017 at 2:30 PM, Tushar Gosavi wrote: > These errors went away after switching to 1.7 version of java for build. > > Thanks, > -Tushar. > > > On

Re: Towards Apache Apex 3.6.0 release

These errors went away after switching to 1.7 version of java for build. Thanks, -Tushar. On Wed, Apr 26, 2017 at 12:50 PM, Tushar Gosavi wrote: > I am following process specified at http://apex.apache.org/release.html to > prepare a release candidate for 3.6. > > I am

Re: Towards Apache Apex 3.6.0 release

I am following process specified at http://apex.apache.org/release.html to prepare a release candidate for 3.6. I am getting error while executing command mvn clean apache-rat:check deploy -Papache-release -DskipTests 100 warnings [INFO]

Re: Towards Apache Apex 3.6.0 release

Why is APEXCORE-700 blocking the release? It is an improvement to a new, evolving feature. IMO this can go into next release. On Mon, Apr 24, 2017 at 12:55 PM, Pramod Immaneni wrote: > Hi, > > APEXCORE-641 has been fixed and I marked it resolved. I have moved my PR >

Re: Towards Apache Apex 3.6.0 release

Hi, APEXCORE-641 has been fixed and I marked it resolved. I have moved my PR which I believe may result in a minor improvement from the blocking path. Thanks On Mon, Apr 24, 2017 at 12:24 PM, Tushar Gosavi wrote: > Hi All, > > I am going to cut first RC in few days.

Re: Towards Apache Apex 3.6.0 release

Hi All, I am going to cut first RC in few days. There are two JIRA pending APEXCORE-700 and APEXCORE-641. APEXCORE-700 is close to merge. @Vlad, Can we move APEXCORE-641 out of 3.6? List of 3.6 issues. https://issues.apache.org/jira/browse/APEXCORE/fixforversion

Re: Towards Apache Apex 3.6.0 release

Vlad, Here is my thought process about these tickets. Both 692 (Apex dev setup sandbox section to reference Apex website downloads page) and 687 (update supported Hadoop v2.6 in Apex docs) are Apex documentation issues, and so they are part of the Apex release process. Furthermore, 692 directly

Re: Towards Apache Apex 3.6.0 release

If there are JIRAs that should be completed, then those should be marked with the fix version so that a report can be run. IMO such items should only be added when they are either critical for the release or will be completed in the next couple of days. On Thu, Apr 13, 2017 at 7:27 PM, Vlad

Re: Towards Apache Apex 3.6.0 release

Dean, 692 and 693 are web site documentation issues and are not part of the Apex core 3.6.0 release. 687 can be covered in the release README (known issues). Thank you, Vlad On 4/13/17 14:11, Dean Lockgaard wrote: I'd like to request that 687, 692 and 693 be included in the 3.6.0 release.

Re: Towards Apache Apex 3.6.0 release

I'd like to request that 687, 692 and 693 be included in the 3.6.0 release. I will send PRs for these shortly. Thanks, Dean On Fri, Apr 14, 2017 at 5:05 AM, Amol Kekre wrote: > +1 to cut a release > > Thks > Amol > > > E:a...@datatorrent.com | M: 510-449-2606 |

Re: Towards Apache Apex 3.6.0 release

+1 to cut a release Thks Amol E:a...@datatorrent.com | M: 510-449-2606 | Twitter: @*amolhkekre* www.datatorrent.com On Thu, Apr 13, 2017 at 9:22 AM, Pramod Immaneni wrote: > +1 > > I would like to see 699 and 700 addressed as well. > > On Wed, Apr 12, 2017 at 10:16

Re: Towards Apache Apex 3.6.0 release

+1 I would like to see 699 and 700 addressed as well. On Wed, Apr 12, 2017 at 10:16 PM, Tushar Gosavi wrote: > Hi, > > It has been four month since 3.5.0 Apex Core release. There are several new > features added to core after 3.5.0. I would like to propose the 3.6.0 >

Re: Towards Apache Apex 3.6.0 release

+1 to cut the release. APEXCORE-678 is optional as it is not a regression and there is no PR open for it. It should not block the release. Thank you, Vlad On 4/12/17 22:16, Tushar Gosavi wrote: Hi, It has been four month since 3.5.0 Apex Core release. There are several new features added

Towards Apache Apex 3.6.0 release

Hi, It has been four month since 3.5.0 Apex Core release. There are several new features added to core after 3.5.0. I would like to propose the 3.6.0 release of Apex Core, to make these features available to users. The list of issues fixed in 3.6.0 are: