Yep, we've already told the existing lists that there will be a move soon.
Once we have access to the new lists, we'll send another message saying
we've made the move.  Then we can shut down the existing lists a little
while after.

Currently, the only work being done is Alan's refactoring job to change the
code from org.jsecurity.* to org.apache.ki.*.  Since this is signifanct,
there are no other developers touching the repository. When he's done with
that, we can move over to SVN at that point.

Here is the Jira issue:  https://issues.apache.org/jira/browse/INFRA-1937

Please let me know if there is anything else.

Thanks for the help!

Les

On Thu, Mar 12, 2009 at 9:30 AM, Brett Porter <[email protected]> wrote:

> We can help do both, just file an issue here:
> https://issues.apache.org/jira/browse/INFRA
>
> You will probably want to notify the lists about the rename with a bit of
> time beforehand.
>
> The SVN move should be coordinated a bit more closely so it doesn't
> interrupt anyone's work. Someone from the project should be on hand to fix
> hudson at the same time.
>
> Cheers,
> Brett
>
> On 11/03/2009, at 7:34 AM, Les Hazlewood wrote:
>
> We'll also need to change Hudson as well.
>
> On Tue, Mar 10, 2009 at 1:20 PM, Alan D. Cabrera <[email protected]>wrote:
>
>> The incubator project JSecurity has voted to change its name.  We have
>> already/will moved the Jira issues and Confluence.
>>
>> I am wondering about the mailing lists SVN setup.  What steps should we
>> take?
>>
>>
>> Regards,
>> Alan
>>
>
>
>  --
> Brett Porter
> [email protected]
> http://blogs.exist.com/bporter/
>
>

Reply via email to