I've unsubscribed from issues@ because I can't handle the sheer volume of
e-mail from it.  In HDFS, they have newly-created issues get sent to
dev@hdfs and people can then choose to watch them for subsequent
notifications.  Notifications will also get sent to dev@ when the JIRA is
closed, but not for any of the updates in between.  I've found that to be a
superior way of staying afloat of the issues I am interested in.  What do
we think about moving to that system for HBase?

Regards,

- Dave

+1 for just CREATED, RESOLVED, and CLOSED.

Since HBase doesn't close issues until a release we need status updates for
resolution too.
On Wednesday, December 5, 2012, Dave Wang wrote:

> I've unsubscribed from issues@ because I can't handle the sheer volume of
> e-mail from it.  In HDFS, they have newly-created issues get sent to
> dev@hdfs and people can then choose to watch them for subsequent
> notifications.  Notifications will also get sent to dev@ when the JIRA is
> closed, but not for any of the updates in between.  I've found that to be a
> superior way of staying afloat of the issues I am interested in.  What do
> we think about moving to that system for HBase?
>
> Regards,
>
> - Dave
>
--
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

I relied heavily on the notifications from issues@ so that I can keep
myself up-to-date on latest development.

Maybe we can create a new mailing list which satisfies Dave's description.

Cheers

On Tue, Dec 4, 2012 at 4:28 PM, Dave Wang <[EMAIL PROTECTED]> wrote:

> I've unsubscribed from issues@ because I can't handle the sheer volume of
> e-mail from it.  In HDFS, they have newly-created issues get sent to
> dev@hdfs and people can then choose to watch them for subsequent
> notifications.  Notifications will also get sent to dev@ when the JIRA is
> closed, but not for any of the updates in between.  I've found that to be a
> superior way of staying afloat of the issues I am interested in.  What do
> we think about moving to that system for HBase?
>
> Regards,
>
> - Dave
>

I just use the RSS feed off JIRA - it keeps track off all the notifications, but doesn't clutter an inbox (and fits in with my daily reading flow).

Maybe an alternative for people?

- Jesse Yates

Sent from my iPhone.

On Dec 4, 2012, at 6:50 PM, Ted Yu <[EMAIL PROTECTED]> wrote:

> I relied heavily on the notifications from issues@ so that I can keep
> myself up-to-date on latest development.
>
> Maybe we can create a new mailing list which satisfies Dave's description.
>
> Cheers
>
> On Tue, Dec 4, 2012 at 4:28 PM, Dave Wang <[EMAIL PROTECTED]> wrote:
>
>> I've unsubscribed from issues@ because I can't handle the sheer volume of
>> e-mail from it.  In HDFS, they have newly-created issues get sent to
>> dev@hdfs and people can then choose to watch them for subsequent
>> notifications.  Notifications will also get sent to dev@ when the JIRA is
>> closed, but not for any of the updates in between.  I've found that to be a
>> superior way of staying afloat of the issues I am interested in.  What do
>> we think about moving to that system for HBase?
>>
>> Regards,
>>
>> - Dave
>>

I want to unsubscribe the dev mail list, but it does not work, who can
help me???
, Jesse Yates 写道:
> I just use the RSS feed off JIRA - it keeps track off all the notifications, but doesn't clutter an inbox (and fits in with my daily reading flow).
>
> Maybe an alternative for people?
>
> - Jesse Yates
>
> Sent from my iPhone.
>
> On Dec 4, 2012, at 6:50 PM, Ted Yu <[EMAIL PROTECTED]> wrote:
>
>> I relied heavily on the notifications from issues@ so that I can keep
>> myself up-to-date on latest development.
>>
>> Maybe we can create a new mailing list which satisfies Dave's description.
>>
>> Cheers
>>
>> On Tue, Dec 4, 2012 at 4:28 PM, Dave Wang <[EMAIL PROTECTED]> wrote:
>>
>>> I've unsubscribed from issues@ because I can't handle the sheer volume of
>>> e-mail from it.  In HDFS, they have newly-created issues get sent to
>>> dev@hdfs and people can then choose to watch them for subsequent
>>> notifications.  Notifications will also get sent to dev@ when the JIRA is
>>> closed, but not for any of the updates in between.  I've found that to be a
>>> superior way of staying afloat of the issues I am interested in.  What do
>>> we think about moving to that system for HBase?
>>>
>>> Regards,
>>>
>>> - Dave
>>>

+1 to having this. The amount of activity over the @issues is pretty
high (HBase is a very very active community). Those of us who'd like
to follow issues but not discussions (unless it interests us, in which
case we "watch"), would certainly like to have the dev@ send a
filtered form.

In addition to the states Andrew's posted, if we have to set it up on
a per-state basis, please also add REOPENED.

On Wed, Dec 5, 2012 at 6:32 AM, Andrew Purtell <[EMAIL PROTECTED]> wrote:
> +1 for just CREATED, RESOLVED, and CLOSED.
>
> Since HBase doesn't close issues until a release we need status updates for
> resolution too.
>
>
> On Wednesday, December 5, 2012, Dave Wang wrote:
>
>> I've unsubscribed from issues@ because I can't handle the sheer volume of
>> e-mail from it.  In HDFS, they have newly-created issues get sent to
>> dev@hdfs and people can then choose to watch them for subsequent
>> notifications.  Notifications will also get sent to dev@ when the JIRA is
>> closed, but not for any of the updates in between.  I've found that to be a
>> superior way of staying afloat of the issues I am interested in.  What do
>> we think about moving to that system for HBase?
>>
>> Regards,
>>
>> - Dave
>>
>
>
> --
> Best regards,
>
>    - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)

--
Harsh J

Thanks Harsh, my apologies for overlooking REOPENED.
On Wed, Dec 5, 2012 at 12:38 PM, Harsh J <[EMAIL PROTECTED]> wrote:

> +1 to having this. The amount of activity over the @issues is pretty
> high (HBase is a very very active community). Those of us who'd like
> to follow issues but not discussions (unless it interests us, in which
> case we "watch"), would certainly like to have the dev@ send a
> filtered form.
>
> In addition to the states Andrew's posted, if we have to set it up on
> a per-state basis, please also add REOPENED.
>
> On Wed, Dec 5, 2012 at 6:32 AM, Andrew Purtell <[EMAIL PROTECTED]>
> wrote:
> > +1 for just CREATED, RESOLVED, and CLOSED.
> >
> > Since HBase doesn't close issues until a release we need status updates
> for
> > resolution too.
> >
> >
> > On Wednesday, December 5, 2012, Dave Wang wrote:
> >
> >> I've unsubscribed from issues@ because I can't handle the sheer volume
> of
> >> e-mail from it.  In HDFS, they have newly-created issues get sent to
> >> dev@hdfs and people can then choose to watch them for subsequent
> >> notifications.  Notifications will also get sent to dev@ when the JIRA
> is
> >> closed, but not for any of the updates in between.  I've found that to
> be a
> >> superior way of staying afloat of the issues I am interested in.  What
> do
> >> we think about moving to that system for HBase?
> >>
> >> Regards,
> >>
> >> - Dave
> >>
> >
> >
> > --
> > Best regards,
> >
> >    - Andy
> >
> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
> > (via Tom White)
>
>
>
> --
> Harsh J
>

--
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

On Tue, Dec 4, 2012 at 4:28 PM, Dave Wang <[EMAIL PROTECTED]> wrote:

> I've unsubscribed from issues@ because I can't handle the sheer volume of
> e-mail from it.  In HDFS, they have newly-created issues get sent to
> dev@hdfs and people can then choose to watch them for subsequent
> notifications.  Notifications will also get sent to dev@ when the JIRA is
> closed, but not for any of the updates in between.  I've found that to be a
> superior way of staying afloat of the issues I am interested in.  What do
> we think about moving to that system for HBase?
>

I agree it is time to try something different.  The mail in issues is
tending to overwhelm such that the important issues may be overlooked.

St.Ack

On Tue, Dec 4, 2012 at 6:50 PM, Ted Yu <[EMAIL PROTECTED]> wrote:

> I relied heavily on the notifications from issues@ so that I can keep
> myself up-to-date on latest development.
>
>
Can you not do some creative gmail filter foo so all issue edits show up
under a single new issues filter -- those from issues@ and the mail to dev
about created, reopened, and resolved issues?
> Maybe we can create a new mailing list which satisfies Dave's description.
>

My sense is that Dave is speaking for a majority of hbase devs; a group who
want to follow along but at a coarser granularity.  The number of us able
to take the full issues mailing list firehose is shrinking radically.  For
example, I can no longer keep up.

St.Ack

If you can't keep up, nobody can!
On Wed, Dec 5, 2012 at 2:25 PM, Stack <[EMAIL PROTECTED]> wrote:

> On Tue, Dec 4, 2012 at 6:50 PM, Ted Yu <[EMAIL PROTECTED]> wrote:
>
> > I relied heavily on the notifications from issues@ so that I can keep
> > myself up-to-date on latest development.
> >
> >
> Can you not do some creative gmail filter foo so all issue edits show up
> under a single new issues filter -- those from issues@ and the mail to dev
> about created, reopened, and resolved issues?
>
>
> > Maybe we can create a new mailing list which satisfies Dave's
> description.
> >
>
> My sense is that Dave is speaking for a majority of hbase devs; a group who
> want to follow along but at a coarser granularity.  The number of us able
> to take the full issues mailing list firehose is shrinking radically.  For
> example, I can no longer keep up.
>
> St.Ack
>

--
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

+1... too many updates on the issues@ list.

On Tue, Dec 4, 2012 at 10:36 PM, Andrew Purtell <[EMAIL PROTECTED]> wrote:

> If you can't keep up, nobody can!
>
>
> On Wed, Dec 5, 2012 at 2:25 PM, Stack <[EMAIL PROTECTED]> wrote:
>
> > On Tue, Dec 4, 2012 at 6:50 PM, Ted Yu <[EMAIL PROTECTED]> wrote:
> >
> > > I relied heavily on the notifications from issues@ so that I can keep
> > > myself up-to-date on latest development.
> > >
> > >
> > Can you not do some creative gmail filter foo so all issue edits show up
> > under a single new issues filter -- those from issues@ and the mail to
> dev
> > about created, reopened, and resolved issues?
> >
> >
> > > Maybe we can create a new mailing list which satisfies Dave's
> > description.
> > >
> >
> > My sense is that Dave is speaking for a majority of hbase devs; a group
> who
> > want to follow along but at a coarser granularity.  The number of us able
> > to take the full issues mailing list firehose is shrinking radically.
>  For
> > example, I can no longer keep up.
> >
> > St.Ack
> >
>
>
>
> --
> Best regards,
>
>    - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>