Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of animesh.chaturvedi@citrix.com
 designates 66.165.176.89 as permitted sender)
From: Animesh Chaturvedi <animesh.chaturvedi@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Tue, 5 Mar 2013 07:33:26 -0800
Subject: RE: [DISCUSS][Action Required] Timeline for moving jira messages to
 a the issues@ list.
Thread-Topic: [DISCUSS][Action Required] Timeline for moving jira messages
 to a the issues@ list.
Thread-Index: Ac4W1bY2oC+oEa6LQtmv3vtMGzNfUACoTG/AAAAVpYAAAK80wA==
Message-ID: 
 <7A92FF96DF135843B4B608FB576BFC3E012F751823E7@SJCPMAILBOX01.citrite.net>
References: 
 <CAKprHVbvtDkjR2tj33L=CtVUYcB2BYHKNp0AUq6rC_YmzTTZWg@mail.gmail.com>
 <CAKprHVYzpJsB=jEz+2SCo8Bw=EG==DZ=wy1WOONr0_3N5A07HQ@mail.gmail.com>
 <7A92FF96DF135843B4B608FB576BFC3E012F751823D4@SJCPMAILBOX01.citrite.net>
 <97F4356AEA71904482CD192135C038F9011CC1D13A13@BANPMAILBOX01.citrite.net>
In-Reply-To: 
 <97F4356AEA71904482CD192135C038F9011CC1D13A13@BANPMAILBOX01.citrite.net>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Ok looks like I am not getting it. Chip / David when you get a chance can y=
ou check it.

> -----Original Message-----
> From: Radhika Puthiyetath [mailto:radhika.puthiyetath@citrix.com]
> Sent: Tuesday, March 05, 2013 12:01 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [DISCUSS][Action Required] Timeline for moving jira messages=
 to
> a the issues@ list.
>=20
> Hi Animesh,
>=20
> I am getting the JIRA notification mails through cloudstack-
> issues@incubator.apache.org.
>=20
> -Radhika
> -----Original Message-----
> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
> Sent: Tuesday, March 05, 2013 1:27 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [DISCUSS][Action Required] Timeline for moving jira messages=
 to
> a the issues@ list.
>=20
> Dave/ Chip
>=20
> Did we move over to the new mailing list? I don't see email sent  to new
> issues mailing list yet
>=20
> Animesh
>=20
> > -----Original Message-----
> > From: David Nalley [mailto:david@gnsa.us]
> > Sent: Friday, March 01, 2013 3:36 PM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: Re: [DISCUSS][Action Required] Timeline for moving jira
> > messages to a the issues@ list.
> >
> > Folks yet another reminder - it's REALLY time to subscribe to
> > cloudstack- issues@incubator.apache.org
> >
> > Please take 30 seconds of your time to do it now.
> >
> > --David
> >
> > On Wed, Feb 13, 2013 at 11:26 PM, David Nalley <david@gnsa.us> wrote:
> > > Hi folks,
> > >
> > > We agreed during the 4.0 development cycle to shift all tickets
> > > traffic to a dedicated list.
> > > Recently that list has been created.
> > >
> > > This is your notice, that at the end of the month (Feb 28th) I will
> > > be shifting all of the message traffic away from cloudstack-dev and
> > > onto cloudstack-issues.
> > >
> > > Why aren't you doing this immediately?
> > >
> > > Many folks see the current flow of messages. This is a good thing.
> > > We're also in the midst of a development cycle trying to get 4.1.0
> > > out, and there needs to be good visibility. Providing plenty of
> > > notice before the change is the surest way to minimize disruption to
> > > the development cycle.
> > >
> > > What does this mean for you?
> > >
> > > If you care to see the the bug traffic, you will need to be
> > > subscribed to the new issues mailing list.
> > > If you are a committer, the expectation is that you be subscribed to
> > > this mailing list.
> > >
> > > How do I subscribe?
> > >
> > > Subscribing is easy one merely needs to send an email to
> > > cloudstack-issues-subscribe@incubator.apache.org
> > >
> > > Will you be any more reminders?
> > >
> > > Why yes, I'll be sending several emails between now and the
> > > implementation of this change, as well as at least one after the fact=
.
> > > In addition, one or more moderators will be monitoring list
> > > subscription and will likely be reaching out to committers who
> > > aren't subscribed.
> > >
> > > I have questions or concerns...
> > >
> > > Great, please respond to this message (on-list) and lets discuss them=
.
> > >
> > > --David