You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-dev@incubator.apache.org by Stefan Bodewig <bo...@apache.org> on 2007/11/06 05:49:16 UTC
Mailing list organization, next steps
Hi all,
the vote to merge the Ant and Ivy dev lists has passed, so I'll file a
new JIRA ticket with the following steps:
1) move ivy-user@incubator to ivy-user@ant keeping all subscribers
2) shut down ivy-private@incubator, forward any mails going there to
private@ant for a few months. People are supposed to subscribe to
private@ant manually (which everybody has done anyway now).
3) shut down ivy-dev@incubator, forward any mails going there to
dev@ant for a few months. I'll ask whether it is possible to
automatically subscribe the current subscribers to dev@ant.
4) shut down ivy-commits@incubator, forward any mails going there to
notifications@ant for a few months. People are supposed to subscribe
to notifications@ant manually. This certainly implies that
notifications@ant has been created by then.
Does anybody see any mistakes in this?
Stefan
Re: Mailing list organization, next steps
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 6 Nov 2007, Dominique Devienne <dd...@gmail.com> wrote:
> 5) shut down ant-cvs@ant, create notifications@ant, then start
> forwarding SVN commit and Wiki changes to notifications@ant?
Hmm, for some reason I totally don't remember that there is a separate
list for commits already. Thanks
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Mailing list organization, next steps
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 29 Nov 2007, Gilles Scokart <gs...@gmail.com> wrote:
> I guess the point 1, 2, 3 can be done now.
Yes, will be requested later today.
> I will send a mail to ivy-commits to tell people to register to
> notification@ant.
Thank you Gilles, but I guess it may be more efficient if you leave it
to me (since I'll be the one who opens the JIRA issues and keeps track
of them).
Stefan
Re: Mailing list organization, next steps
Posted by Gilles Scokart <gs...@gmail.com>.
I guess the point 1, 2, 3 can be done now.
For 4 and 5 I guess it is better to wait that the people register to the new
list.
If is is not authorized to automatically migrate users from ivy-dev to
dev@ant, then we might have to wait a little bit as well.
I will send a mail to ivy-commits to tell people to register to
notification@ant.
Gilles
2007/11/6, Dominique Devienne <dd...@gmail.com>:
>
> On 11/5/07, Stefan Bodewig <bo...@apache.org> wrote:
> > Hi all,
> >
> > the vote to merge the Ant and Ivy dev lists has passed, so I'll file a
> > new JIRA ticket with the following steps:
> >
> > 1) move ivy-user@incubator to ivy-user@ant keeping all subscribers
> >
> > 2) shut down ivy-private@incubator, forward any mails going there to
> > private@ant for a few months. People are supposed to subscribe to
> > private@ant manually (which everybody has done anyway now).
> >
> > 3) shut down ivy-dev@incubator, forward any mails going there to
> > dev@ant for a few months. I'll ask whether it is possible to
> > automatically subscribe the current subscribers to dev@ant.
> >
> > 4) shut down ivy-commits@incubator, forward any mails going there to
> > notifications@ant for a few months. People are supposed to subscribe
> > to notifications@ant manually. This certainly implies that
> > notifications@ant has been created by then.
> >
>
> 5) shut down ant-cvs@ant, create notifications@ant, then start
> forwarding SVN commit and Wiki changes to notifications@ant?
>
> --DD
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
--
Gilles Scokart
Re: Mailing list organization, next steps
Posted by Gilles Scokart <gs...@gmail.com>.
I guess the point 1, 2, 3 can be done now.
For 4 and 5 I guess it is better to wait that the people register to the new
list.
If is is not authorized to automatically migrate users from ivy-dev to
dev@ant, then we might have to wait a little bit as well.
I will send a mail to ivy-commits to tell people to register to
notification@ant.
Gilles
2007/11/6, Dominique Devienne <dd...@gmail.com>:
>
> On 11/5/07, Stefan Bodewig <bo...@apache.org> wrote:
> > Hi all,
> >
> > the vote to merge the Ant and Ivy dev lists has passed, so I'll file a
> > new JIRA ticket with the following steps:
> >
> > 1) move ivy-user@incubator to ivy-user@ant keeping all subscribers
> >
> > 2) shut down ivy-private@incubator, forward any mails going there to
> > private@ant for a few months. People are supposed to subscribe to
> > private@ant manually (which everybody has done anyway now).
> >
> > 3) shut down ivy-dev@incubator, forward any mails going there to
> > dev@ant for a few months. I'll ask whether it is possible to
> > automatically subscribe the current subscribers to dev@ant.
> >
> > 4) shut down ivy-commits@incubator, forward any mails going there to
> > notifications@ant for a few months. People are supposed to subscribe
> > to notifications@ant manually. This certainly implies that
> > notifications@ant has been created by then.
> >
>
> 5) shut down ant-cvs@ant, create notifications@ant, then start
> forwarding SVN commit and Wiki changes to notifications@ant?
>
> --DD
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
--
Gilles Scokart
Re: Mailing list organization, next steps
Posted by Dominique Devienne <dd...@gmail.com>.
On 11/5/07, Stefan Bodewig <bo...@apache.org> wrote:
> Hi all,
>
> the vote to merge the Ant and Ivy dev lists has passed, so I'll file a
> new JIRA ticket with the following steps:
>
> 1) move ivy-user@incubator to ivy-user@ant keeping all subscribers
>
> 2) shut down ivy-private@incubator, forward any mails going there to
> private@ant for a few months. People are supposed to subscribe to
> private@ant manually (which everybody has done anyway now).
>
> 3) shut down ivy-dev@incubator, forward any mails going there to
> dev@ant for a few months. I'll ask whether it is possible to
> automatically subscribe the current subscribers to dev@ant.
>
> 4) shut down ivy-commits@incubator, forward any mails going there to
> notifications@ant for a few months. People are supposed to subscribe
> to notifications@ant manually. This certainly implies that
> notifications@ant has been created by then.
>
5) shut down ant-cvs@ant, create notifications@ant, then start
forwarding SVN commit and Wiki changes to notifications@ant?
--DD
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Mailing list organization, next steps
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 6 Nov 2007, Xavier Hanin <xa...@gmail.com> wrote:
> Is the notification list already created, and ant notification
> e-mails already redirected to it rather than dev@ant?
No.
> Because I think if we auto subscribe ivy-dev subscribers to dev@ant,
> some would be annoyed by the volume of notification e-mails if
> things are not done in the right order.
OK, so I'll wait until the notifications list is up and running.
Thanks
Stefan
Re: Mailing list organization, next steps
Posted by Xavier Hanin <xa...@gmail.com>.
On 11/6/07, Stefan Bodewig <bo...@apache.org> wrote:
>
> Hi all,
>
> the vote to merge the Ant and Ivy dev lists has passed, so I'll file a
> new JIRA ticket with the following steps:
>
> 1) move ivy-user@incubator to ivy-user@ant keeping all subscribers
>
> 2) shut down ivy-private@incubator, forward any mails going there to
> private@ant for a few months. People are supposed to subscribe to
> private@ant manually (which everybody has done anyway now).
>
> 3) shut down ivy-dev@incubator, forward any mails going there to
> dev@ant for a few months. I'll ask whether it is possible to
> automatically subscribe the current subscribers to dev@ant.
>
> 4) shut down ivy-commits@incubator, forward any mails going there to
> notifications@ant for a few months. People are supposed to subscribe
> to notifications@ant manually. This certainly implies that
> notifications@ant has been created by then.
>
> Does anybody see any mistakes in this?
Is the notification list already created, and ant notification e-mails
already redirected to it rather than dev@ant? Because I think if we auto
subscribe ivy-dev subscribers to dev@ant, some would be annoyed by the
volume of notification e-mails if things are not done in the right order.
My 2c.
Xavier
Stefan
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/
Re: Mailing list organization, next steps
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 6 Nov 2007, Gilles Scokart <gs...@gmail.com> wrote:
> No mistakes, provided that every step is immediately preceded by a
> mail on this mailing list explaining what will happen to the list.
I'd send out such mails when I create the JIRA issues since I don't
know when the change is going to happen after that.
> Also, what will happen with the public archives?
They'll remain where they are. I think the archive for ivy-user will
migrate to be listed under ant.apache.org.
If you are talking about a different archive than Apache's, they'll
probably work and list the old addresses since their receivers rmain
subscribed.
Stefan
Re: Mailing list organization, next steps
Posted by Gilles Scokart <gs...@gmail.com>.
No mistakes, provided that every step is immediately preceded by a mail on
this mailing list explaining what will happen to the list.
Also, what will happen with the public archives?
Gilles
2007/11/6, Stefan Bodewig <bo...@apache.org>:
>
> Hi all,
>
> the vote to merge the Ant and Ivy dev lists has passed, so I'll file a
> new JIRA ticket with the following steps:
>
> 1) move ivy-user@incubator to ivy-user@ant keeping all subscribers
>
> 2) shut down ivy-private@incubator, forward any mails going there to
> private@ant for a few months. People are supposed to subscribe to
> private@ant manually (which everybody has done anyway now).
>
> 3) shut down ivy-dev@incubator, forward any mails going there to
> dev@ant for a few months. I'll ask whether it is possible to
> automatically subscribe the current subscribers to dev@ant.
>
> 4) shut down ivy-commits@incubator, forward any mails going there to
> notifications@ant for a few months. People are supposed to subscribe
> to notifications@ant manually. This certainly implies that
> notifications@ant has been created by then.
>
> Does anybody see any mistakes in this?
>
> Stefan
>
--
Gilles SCOKART