Return-Path: 
 <dev-return-1089-apmail-zest-dev-archive=zest.apache.org@zest.apache.org>
X-Original-To: apmail-zest-dev-archive@minotaur.apache.org
Delivered-To: apmail-zest-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 3303C185C8
	for <apmail-zest-dev-archive@minotaur.apache.org>;
 Fri, 31 Jul 2015 03:37:05 +0000 (UTC)
Received: (qmail 34955 invoked by uid 500); 31 Jul 2015 03:37:05 -0000
Delivered-To: apmail-zest-dev-archive@zest.apache.org
Received: (qmail 34882 invoked by uid 500); 31 Jul 2015 03:37:05 -0000
Mailing-List: contact dev-help@zest.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@zest.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@zest.apache.org>
List-Post: <mailto:dev@zest.apache.org>
List-Id: <dev.zest.apache.org>
Reply-To: dev@zest.apache.org
Delivered-To: mailing list dev@zest.apache.org
Received: (qmail 34655 invoked by uid 99); 31 Jul 2015 03:37:05 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Jul 2015 03:37:05 +0000
Date: Fri, 31 Jul 2015 03:37:04 +0000 (UTC)
From: "Niclas Hedhman (JIRA)" <jira@apache.org>
To: dev@zest.apache.org
Message-ID: <JIRA.12850494.1438313135000.336938.1438313824959@Atlassian.JIRA>
In-Reply-To: <JIRA.12850494.1438313135000@Atlassian.JIRA>
References: <JIRA.12850494.1438313135000@Atlassian.JIRA>
 <JIRA.12850494.1438313135857@arcas>
Subject: [jira] [Updated] (ZEST-109) 3.0 Epic
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/ZEST-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Niclas Hedhman updated ZEST-109:
--------------------------------
    Description: 
We have discussed many major design efforts for Zest 3.0. It is not likely that they are all feasible in one go, and it is hard to prioritize at this stage. This Epic is only the placeholder for the big design efforts scheduled for 3.0 or later. Each constituent should be linked with 'is part of' this issue.


  was:
We have discussed many major design efforts for Zest 3.0. It is not likely that they are all feasible in one go, and it is hard to prioritize at this stage. This Epic is only the placeholder for the big design efforts scheduled for 3.0 or later. Each constituent should be linked with 'is part of' this issue.

<<Click 'ALL' in the 'Activity' tabs below to view the issues linked.>>


> 3.0 Epic
> --------
>
>                 Key: ZEST-109
>                 URL: https://issues.apache.org/jira/browse/ZEST-109
>             Project: Zest
>          Issue Type: New Feature
>            Reporter: Niclas Hedhman
>
> We have discussed many major design efforts for Zest 3.0. It is not likely that they are all feasible in one go, and it is hard to prioritize at this stage. This Epic is only the placeholder for the big design efforts scheduled for 3.0 or later. Each constituent should be linked with 'is part of' this issue.



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