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.63 as permitted sender)
From: Animesh Chaturvedi <animesh.chaturvedi@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Mon, 25 Feb 2013 22:49:59 -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: Ac4Ka56gG1oXFlgMR2W+KIUo8s2xvQJgbcJw
Message-ID: 
 <7A92FF96DF135843B4B608FB576BFC3E012F74C411AD@SJCPMAILBOX01.citrite.net>
References: 
 <CAKprHVbvtDkjR2tj33L=CtVUYcB2BYHKNp0AUq6rC_YmzTTZWg@mail.gmail.com>
In-Reply-To: 
 <CAKprHVbvtDkjR2tj33L=CtVUYcB2BYHKNp0AUq6rC_YmzTTZWg@mail.gmail.com>
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

Folks=20

We are approaching the deadline for switch to new Jira mailing list on 2/28=
. If you are not subscribed yet, please do so.

Thanks
Animesh

> -----Original Message-----
> From: David Nalley [mailto:david@gnsa.us]
> Sent: Wednesday, February 13, 2013 8:27 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: [DISCUSS][Action Required] Timeline for moving jira messages to =
a the
> issues@ list.
>=20
> Hi folks,
>=20
> We agreed during the 4.0 development cycle to shift all tickets traffic t=
o a
> dedicated list.
> Recently that list has been created.
>=20
> This is your notice, that at the end of the month (Feb 28th) I will be sh=
ifting all
> of the message traffic away from cloudstack-dev and onto cloudstack-issue=
s.
>=20
> Why aren't you doing this immediately?
>=20
> 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, a=
nd
> there needs to be good visibility. Providing plenty of notice before the =
change is
> the surest way to minimize disruption to the development cycle.
>=20
> What does this mean for you?
>=20
> 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.
>=20
> How do I subscribe?
>=20
> Subscribing is easy one merely needs to send an email to cloudstack-issue=
s-
> subscribe@incubator.apache.org
>=20
> Will you be any more reminders?
>=20
> Why yes, I'll be sending several emails between now and the implementatio=
n 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.
>=20
> I have questions or concerns...
>=20
> Great, please respond to this message (on-list) and lets discuss them.
>=20
> --David