Return-Path: X-Original-To: apmail-apex-dev-archive@minotaur.apache.org Delivered-To: apmail-apex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6C3481839C for ; Tue, 5 Jan 2016 09:10:46 +0000 (UTC) Received: (qmail 74505 invoked by uid 500); 5 Jan 2016 09:10:46 -0000 Delivered-To: apmail-apex-dev-archive@apex.apache.org Received: (qmail 74443 invoked by uid 500); 5 Jan 2016 09:10:46 -0000 Mailing-List: contact dev-help@apex.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@apex.incubator.apache.org Delivered-To: mailing list dev@apex.incubator.apache.org Received: (qmail 74431 invoked by uid 99); 5 Jan 2016 09:10:45 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jan 2016 09:10:45 +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 806481A03D6 for ; Tue, 5 Jan 2016 09:10:45 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3 X-Spam-Level: *** X-Spam-Status: No, score=3 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=datatorrent-com.20150623.gappssmtp.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id Kz1V-I83iXip for ; Tue, 5 Jan 2016 09:10:36 +0000 (UTC) Received: from mail-lf0-f50.google.com (mail-lf0-f50.google.com [209.85.215.50]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 01ED124E30 for ; Tue, 5 Jan 2016 09:10:35 +0000 (UTC) Received: by mail-lf0-f50.google.com with SMTP id z124so285246369lfa.3 for ; Tue, 05 Jan 2016 01:10:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=datatorrent-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=3gDBuEqYg/mtrPjGceYdNU+1k7I7XsT1huzzv9f38NY=; b=BsPlugpAzdpyxMB0v3qOcLpUG030M0XsIuKkm/Q8wMv3+CG5BHZCQkMoa/JFCw4aGr eb8QL/4gbxW+eWH/oQHlqHPpB0QPcJXILg5gsUkA5v2vo4QJf7QDuLeZun7f5OaNTXvB DT6ZBR9DZdcDFOyKdQPm3wN/jlwCykj9zzgfOMXyTUm4r0yysGUXvXUi6BY5kadXIt1v 8fSHpWOT/4QxMqWNFY14kXevzcosp9oGWfYrXh9ejlloyqAz+WpNbr9MdpyQKzOvRnWd cuWieezSHFNKjqMnGkdzCLHZYeyF9A6T0/8MhjrElCSi6KT+Oy8nJyg3FdLFZDekSHjE +jyg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=3gDBuEqYg/mtrPjGceYdNU+1k7I7XsT1huzzv9f38NY=; b=RgOYgZnEiTcIh0GeroWoSp3/uFsftu9o7x8jE22Nqme+kE8+i3nMBg9NIG3MVXIKz3 lgeGzLjAXx7H62vI8oNzDLMC9K17Ip5Y0AP0HmzMwrIX1EU5PEdbXAasIPtJVG/XQ7ZY k7r2ucNVtNeaauw9lvy6I/IqQyUDBbHn9OM9dKrzSSTYXB7Au+h5cFwGvPA3tKr+AHhp 5rwZB+0BdYZWziZpOVtY9fDmqQ7xJOWlqH27UbjCFYuKtB5rHUdif7AIw7/e4FWeeiZo d3TArFPZpvZfXjpLN+bI0vHub+uHSgJDUNR46QBbfDeV0gOT1aF3r7hQe6kqQDVEISYP wMHQ== X-Gm-Message-State: ALoCoQlMqCRjJXpeOwd1MWN5BVucLjaG0KpWFJ8FSkD1moEWvcV2vQSMDG9/pwOpV6IJPbKCzZBzlvVj19/kSuMfcExgCmFInNShTFWCOWjoBZpsmdJWUaU= MIME-Version: 1.0 X-Received: by 10.25.145.81 with SMTP id t78mr33302875lfd.86.1451985035137; Tue, 05 Jan 2016 01:10:35 -0800 (PST) Received: by 10.25.150.139 with HTTP; Tue, 5 Jan 2016 01:10:35 -0800 (PST) In-Reply-To: References: Date: Tue, 5 Jan 2016 14:40:35 +0530 Message-ID: Subject: Re: Apex Core JIRA migration From: Yogi Devendra To: dev@apex.incubator.apache.org Content-Type: multipart/alternative; boundary=001a1140043c3d354f0528929ced --001a1140043c3d354f0528929ced Content-Type: text/plain; charset=UTF-8 When I add 'work log' in JIRA as 2d ; it is translated to 48 hours. Should we keep it like this OR change it to 8 hours per day? ~ Yogi On Tue, Jan 5, 2016 at 1:11 PM, Thomas Weise wrote: > The user was automatically created during migration (you did not supply a > user mapping). > > On Mon, Jan 4, 2016 at 10:25 PM, Yogi Devendra < > devendra.vyavahare@gmail.com > > wrote: > > > Opps. I am not aware of when devendra@datatorrent.com got created on the > > apache JIRA. > > > > devendra@datatorrent.com ID is working fine after reset password. > > > > Thanks a lot. > > > > ~ Yogi > > > > On 5 January 2016 at 11:19, Thomas Weise wrote: > > > > > That won't work. Do a password reset with the correct email ID and get > > rid > > > of the duplicate account please. > > > > > > On Mon, Jan 4, 2016 at 9:46 PM, Yogi Devendra < > > > devendra.vyavahare@gmail.com> > > > wrote: > > > > > > > original ticket was assigned to devendra@datatorrent.com > > > > > > > > Now, I am logging in as yogidevendra@apache.org. > > > > Because, devendra@datatorrent.com with the password on > > > > https://malhar.atlassian.net does not work on new JIRA on > > > > https://issues.apache.org/jira/browse/APEXMALHAR. > > > > > > > > ~ Yogi > > > > > > > > On 5 January 2016 at 11:10, Thomas Weise > > wrote: > > > > > > > > > Is it possible that you are logged in as a different user? > > > > > > > > > > > > > > > On Mon, Jan 4, 2016 at 9:30 PM, Yogi Devendra < > > > > > devendra.vyavahare@gmail.com> > > > > > wrote: > > > > > > > > > > > No. I am not able to see 'start-progress' button. > > > > > > > > > > > > I have commented on INFRA jira ticket with the screenshot. > > > > > > > > > > > > ~ Yogi > > > > > > > > > > > > On 5 January 2016 at 10:45, Thomas Weise > > > > > wrote: > > > > > > > > > > > > > You are in the committer role and should be able to do this. Do > > you > > > > see > > > > > > the > > > > > > > "Start Progress" button? > > > > > > > > > > > > > > Please log the issue here: > > > > > > > > > > > > > > https://issues.apache.org/jira/browse/INFRA-10144 > > > > > > > > > > > > > > > > > > > > > On Mon, Jan 4, 2016 at 9:06 PM, Yogi Devendra < > > > > yogidevendra@apache.org > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > I am working on this ticket: > > > > > > > > > > > > > > > > https://issues.apache.org/jira/browse/APEXMALHAR-1958 > > > > > > > > > > > > > > > > But, I am not able to move it from 'open' to 'in-progress'. > > > > > > > > Also, not able to add work log. > > > > > > > > > > > > > > > > Is anyone else facing similar issue after migration of Malhar > > > JIRA? > > > > > > > > Any suggestions for this? > > > > > > > > > > > > > > > > ~ Yogi > > > > > > > > > > > > > > > > > > > > > > > > ~ Yogi > > > > > > > > > > > > > > > > On 3 January 2016 at 15:18, Thomas Weise < > > thomas@datatorrent.com > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > The JIRA migration for Malhar is complete: > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/browse/APEXMALHAR > > > > > > > > > > > > > > > > > > The old instance is readonly. > > > > > > > > > > > > > > > > > > Thomas > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Dec 11, 2015 at 10:35 AM, Thomas Weise < > > > > > > thomas@datatorrent.com > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > It is tracked here: > > > > > > > https://issues.apache.org/jira/browse/INFRA-10144 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Dec 11, 2015 at 10:15 AM, David Yan < > > > > > david@datatorrent.com > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > >> There is a slight problem. The previously resolved JIRAs > > are > > > > > > > > > "unresolved". > > > > > > > > > >> Example: > > > > > > > > > >> > > > > > > > > > >> https://issues.apache.org/jira/browse/APEXCORE-24 vs > > > > > > > > > >> https://malhar.atlassian.net/browse/APEX-24 > > > > > > > > > >> > > > > > > > > > >> APEXCORE-24 has Status: resolved, Resolution: > unresolved. > > > > > > > > > >> APEX-24 has Status: resolved, Resolution: fixed. > > > > > > > > > >> > > > > > > > > > >> As a result, common filters in APEXCORE that only list > > > > > unresolved > > > > > > > > > tickets > > > > > > > > > >> are now listing previously resolved tickets. > > > > > > > > > >> > > > > > > > > > >> David > > > > > > > > > >> > > > > > > > > > >> On Mon, Dec 7, 2015 at 8:40 AM, Thomas Weise < > > > > > > > thomas@datatorrent.com> > > > > > > > > > >> wrote: > > > > > > > > > >> > > > > > > > > > >> > Should work, but now it will be APEXCORE-123 instead > of > > > > > APEX-123 > > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > > > >> > On Mon, Dec 7, 2015 at 8:14 AM, Siyuan Hua < > > > > > > > siyuan@datatorrent.com> > > > > > > > > > >> wrote: > > > > > > > > > >> > > > > > > > > > > >> > > Can we use same git commit message to > resolve/comment > > on > > > > the > > > > > > > issue > > > > > > > > > >> > > > > > > > > > > > >> > > On Sun, Dec 6, 2015 at 2:07 PM, Thomas Weise < > > > > > > > > > thomas@datatorrent.com> > > > > > > > > > >> > > wrote: > > > > > > > > > >> > > > > > > > > > > > >> > > > Please start using the ASF JIRA for core: > > > > > > > > > >> > > > > > > > > > > > > >> > > > https://issues.apache.org/jira/browse/APEXCORE/ > > > > > > > > > >> > > > > > > > > > > > > >> > > > You may have to create a login is you have not > > already > > > > > done > > > > > > > so. > > > > > > > > If > > > > > > > > > >> you > > > > > > > > > >> > > have > > > > > > > > > >> > > > access related problems, contact me. > > > > > > > > > >> > > > > > > > > > > > > >> > > > There were a few issues with the migration, > > including > > > > > > > > fixedVersion > > > > > > > > > >> and > > > > > > > > > >> > > > resolution fields. Those should be fixed soon and > > > don't > > > > > > affect > > > > > > > > > work > > > > > > > > > >> > with > > > > > > > > > >> > > > current issues. All migrated issues have a link to > > the > > > > old > > > > > > > JIRA > > > > > > > > > >> added. > > > > > > > > > >> > > > > > > > > > > > > >> > > > Malhar will move work will start once the > migration > > > > > process > > > > > > it > > > > > > > > > >> tuned. > > > > > > > > > >> > > Until > > > > > > > > > >> > > > then continue to use the old JIRA instance (for > > Malhar > > > > > > only): > > > > > > > > > >> > > > > > > > > > > > > >> > > > > https://malhar.atlassian.net/projects/MLHR/issues/ > > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > Thomas > > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > On Sat, Dec 5, 2015 at 12:49 AM, Amol Kekre < > > > > > > > > amol@datatorrent.com > > > > > > > > > > > > > > > > > > > >> > > wrote: > > > > > > > > > >> > > > > > > > > > > > > >> > > > > Great news. Nice > > > > > > > > > >> > > > > > > > > > > > > > >> > > > > Thks > > > > > > > > > >> > > > > Amol > > > > > > > > > >> > > > > > > > > > > > > > >> > > > > On Fri, Dec 4, 2015 at 3:22 PM, Thomas Weise < > > > > > > > > > >> thomas@datatorrent.com > > > > > > > > > >> > > > > > > > > > > > >> > > > > wrote: > > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > Gavin from the infrastructure group is going > to > > > > > migrate > > > > > > > the > > > > > > > > > Apex > > > > > > > > > >> > core > > > > > > > > > >> > > > > JIRA > > > > > > > > > >> > > > > > to ASF this weekend. We will make it readonly > > now > > > > and > > > > > > send > > > > > > > > an > > > > > > > > > >> > update > > > > > > > > > >> > > > when > > > > > > > > > >> > > > > > the new instance is ready. > > > > > > > > > >> > > > > > > > > > > > > > > >> > > > > > Thanks, > > > > > > > > > >> > > > > > Thomas > > > > > > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --001a1140043c3d354f0528929ced--