Return-Path: 
 <esme-dev-return-2570-apmail-incubator-esme-dev-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org
Received: (qmail 93680 invoked from network); 7 Jan 2010 22:47:23 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 7 Jan 2010 22:47:23 -0000
Received: (qmail 89371 invoked by uid 500); 7 Jan 2010 22:47:23 -0000
Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org
Received: (qmail 89312 invoked by uid 500); 7 Jan 2010 22:47:23 -0000
Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:esme-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:esme-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:esme-dev@incubator.apache.org>
List-Id: <esme-dev.incubator.apache.org>
Reply-To: esme-dev@incubator.apache.org
Delivered-To: mailing list esme-dev@incubator.apache.org
Received: (qmail 89302 invoked by uid 99); 7 Jan 2010 22:47:23 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jan 2010 22:47:23 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of yojibee@gmail.com designates
 209.85.219.210 as permitted sender)
Received: from [209.85.219.210] (HELO mail-ew0-f210.google.com)
 (209.85.219.210)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jan 2010 22:47:13 +0000
Received: by ewy2 with SMTP id 2so21863367ewy.27
        for <esme-dev@incubator.apache.org>;
 Thu, 07 Jan 2010 14:46:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:content-type:mime-version
         :subject:from:in-reply-to:date:content-transfer-encoding:message-id
         :references:to:x-mailer;
        bh=n6sW5AH10MhDB9nxSlXjtuYLIY47UmK8lK24bQBBQRY=;
        b=K/NrMd7lnWmy3Kyv7ixQSCiCmGA8xxY455IDDVUJm+nKqFHsrOFT4u//RH18CeJTM6
         kGfR8qauuPa7C0rF7NccD2P/mnSV2lpje3Wi9ENsPUULYy1h7kQ069rnLL4Ml7HKupdZ
         JDyFEaVzUh890S4wmkSErbEfqCvvziCmD1qi0=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=eTGtTGStUNikpIBV+Qd6LOtwdMRV23M+fXTIbj41/4BVoR4f5fBWsVOfO2oNcQKoe/
         S8wR5aIrh+aRkSufw67HsUCl0zkg2ml5bhhI7KI5SCuSSU9jnG9nNaCrTczweGb0YV5S
         jneXpa+WSNNoIU9ABDvjYxSvZk1kjHfaj2MoU=
Received: by 10.213.109.69 with SMTP id i5mr398124ebp.11.1262904384997;
        Thu, 07 Jan 2010 14:46:24 -0800 (PST)
Received: from ?192.168.1.39? (s0021-0029.dsl.start.no [77.40.128.221])
        by mx.google.com with ESMTPS id 14sm15484697ewy.7.2010.01.07.14.46.23
        (version=TLSv1/SSLv3 cipher=RC4-MD5);
        Thu, 07 Jan 2010 14:46:24 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1077)
Subject: Re: Issues currently assigned to release 1.0 that I would like to
  change
From: =?iso-8859-1?Q?Anne_Kathrine_Petter=F8e?= <yojibee@gmail.com>
In-Reply-To: <fa2d9f451001071138g58f1ce30if6fec710142872f2@mail.gmail.com>
Date: Thu, 7 Jan 2010 23:46:22 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <83ADF5BA-E232-42B5-8FCF-793EE5BE1A6B@gmail.com>
References: <68f4a0e81001061924o2644374y217c7d270a951b1a@mail.gmail.com>
 <fa2d9f451001071138g58f1ce30if6fec710142872f2@mail.gmail.com>
To: esme-dev@incubator.apache.org
X-Mailer: Apple Mail (2.1077)
X-Virus-Checked: Checked by ClamAV on apache.org

Ethan,

I don't have anything to add to your comments, other than that I agree.
IMO it is more important to get a release shipped, than it being =
technically perfect.

@Dick: AFAIK issue 47 is OK.
Robert says in one of the comments to the task "<snip> Apache prefers =
not to have copyright notices", he doesn't say it is forbidden. Can =
someone (Mentor or anyone else who knows) please confirm this?

What do we do about the streams page?
I don't see why we should remove it, but I think it at least requires a =
better documentation (in the wiki) before it is released.
Even if we decide to keep streams, I don't think #117 would be a =
necessity for release 1.0.

/Anne


On 7. jan. 2010, at 20.38, Richard Hirsch wrote:

> On Thu, Jan 7, 2010 at 4:24 AM, Ethan Jewett <esjewett@gmail.com> =
wrote:
>> Actually, I wrote the last email looking for guidance and then just
>> went through all the Release 1.0 issues and compiled the list of
>> things I want to change.
>>=20
>> I think it's important that we push to get a release out, and part of
>> doing this is having a clear view of what is part of the release. =
When
>> we are pushing for a release, I think it is important to identify =
what
>> *must* go in and what can wait. Generally, if something is not
>> absolutely required, I think it should go in the next release. If
>> someone cares about it and gets a patch in before we release, then
>> great, but if not it shouldn't stop the release. Therefore the =
largest
>> list by far is the list of things I want to move to Release 1.1.
>>=20
>> This is the list of issues I've reviewed and more recommended changes
>> and rationales. Please review and respond if there are things you
>> don't agree with. If there is no objection, I will try to make these
>> changes this weekend.
>>=20
>> Thanks,
>> Ethan
>>=20
>> Change to "Fixed":
>>=20
>> 1. https://issues.apache.org/jira/browse/ESME-53 - Implement access
>> pools <-- Looks to me like this is complete
>> 2. https://issues.apache.org/jira/browse/ESME-40 - Static Texts in
>> Resource File <-- Is this complete? We have Chinese translations
>> already
>=20
>> 3. https://issues.apache.org/jira/browse/ESME-125 - Change Date =
format
>> to make lists sortable: Users and Streams pages <-- This appears to =
be
>> fixed (I've set it to resolved)
>>=20
>>=20
>> Change to "Won't fix":
>>=20
>> 1. https://issues.apache.org/jira/browse/ESME-102 - Ability to add
>> tags to message are missing <-- Tags can be added through hash tags,
>> or API
>> 2. https://issues.apache.org/jira/browse/ESME-47 - Some Licensing =
Nits
>> <-- Seems like the result of the discussion was "Won't fix"
>>=20
> this is an issue that we will have to deal with before we create a =
release.
>>=20
>> Move to Release 1.1:
>>=20
>> 1. https://issues.apache.org/jira/browse/ESME-143 - HTTP Post Actions
>> should post a message with the results of the HTTP post action <--
>> Lack of consensus on proper implementation (keep as patch for release
>> 1.0)
>> 2. https://issues.apache.org/jira/browse/ESME-107 - Harmonize code to
>> display of users <-- Nice to have, not required for release (also
>> blocked by new UI)
>> 3. https://issues.apache.org/jira/browse/ESME-109 - Harmonize
>> tag/found word searches <-- Nice to have, part of new UI build (now
>> linked)
>> 4. https://issues.apache.org/jira/browse/ESME-18 - JMX support <-- =
Nice to have
>> 5. https://issues.apache.org/jira/browse/ESME-16 - Unifying server
>> calls (JSON-related) <-- Seems like a nice to have
>> 6. https://issues.apache.org/jira/browse/ESME-122 - Message when user
>> is deleted from a pool is missing <-- Seems like a nice to have
>> 7. https://issues.apache.org/jira/browse/ESME-119 - Messages for
>> Action Page <-- Nice to have, and needs more discussion
>> 8. https://issues.apache.org/jira/browse/ESME-121 - Messages for
>> Streams Page <-- Nice to have, and needs more discussion
>> 9. https://issues.apache.org/jira/browse/ESME-120 - Messages for =
Track
>> Page are missing <-- Nice to have, and needs more discussion (or
>> perhaps I'm misunderstanding this group of issues)
>>=20
> These are smaller issues that I created for people who were interested
> in contributing but didn't want to start with huge / complicated
> issues
>>=20
>> Needs discussion or more information:
>>=20
>> 1. https://issues.apache.org/jira/browse/ESME-117 - Current Filter
>> Info on Streams page <-- Is this functionality ready for or required
>> for a 1.0 release? Perhaps we should hide streams for the 1.0 =
release?
>> 2. https://issues.apache.org/jira/browse/ESME-152 - Posting with
>> Japanese characters cause problems <-- We need a failing test
>>=20