You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Andrus Adamchik <an...@objectstyle.org> on 2006/05/05 19:41:09 UTC
CVS migration to apache??
Anonymous CVS @SF has been down since March. A number of users have
been complaining that they can't create patches or test their custom
changes because of that. The situation is not critical, but still
rather annoying.
I am thinking maybe we should change our earlier decision to keep 1.2
on SF and move it to Apache SVN now (but of course still keep doing
releases from SF with the current package naming)?
Andrus
Re: JIRA->SVN links (Re: [DONE] Re: Do not check in code until further notice)
Posted by Andrus Adamchik <an...@objectstyle.org>.
Jeff,
I was about to ask you to do that. You are ahead of me :-)
Thanks
Andrus
On May 7, 2006, at 8:49 PM, Jeff Turner wrote:
> On Sun, May 07, 2006 at 11:03:02AM -0400, Andrus Adamchik wrote:
>> Migration is successfully completed. Check ins can resume to the new
>> location at https://svn.apache.org/repos/asf/incubator/cayenne/main/
>> trunk/cayenne/
>
> I've enabled the JIRA Subversion integration. Eg:
>
> http://issues.apache.org/cayenne/browse/CAY-261?page=all
> http://issues.apache.org/cayenne/browse/CAY-470?page=all
> http://issues.apache.org/cayenne/browse/CAY-207?page=all
>
> There are plenty of examples, as Andrus has been very good about
> recording issue keys in commits.
>
>
> --Jeff
>
>> Andrus
>>
>>
>> On May 6, 2006, at 4:12 PM, Andrus Adamchik wrote:
>>
>>> I am migrating CVS now. Do not check in code until further notice.
>>>
>>> As the CVS tarball from SF is old, I'll do a local merge of the
>>> HEAD code into it. The worst scenario - we'll loose the last Beta
>>> tag - no big deal. I recently did this operation with WOProject CVS
>>> - it worked pretty well.
>>>
>>> Andrus
>>>
>>>
>>> On May 5, 2006, at 1:47 PM, Cris Daniluk wrote:
>>>
>>>> My favorite part of SVN is the fact that the repository can easily
>>>> evolve... directories are not only movable, but revision history is
>>>> preserved. We can just branch when we're ready and change like
>>>> crazy.
>>>>
>>>> I'm definitely +1
>>>>
>>>> On 5/5/06, Andrus Adamchik <an...@objectstyle.org> wrote:
>>>>> Anonymous CVS @SF has been down since March. A number of users
>>>>> have
>>>>> been complaining that they can't create patches or test their
>>>>> custom
>>>>> changes because of that. The situation is not critical, but still
>>>>> rather annoying.
>>>>>
>>>>> I am thinking maybe we should change our earlier decision to keep
>>>>> 1.2
>>>>> on SF and move it to Apache SVN now (but of course still keep
>>>>> doing
>>>>> releases from SF with the current package naming)?
>>>>>
>>>>> Andrus
>>>>>
>>>>
>>>
>>>
>
JIRA->SVN links (Re: [DONE] Re: Do not check in code until further notice)
Posted by Jeff Turner <je...@apache.org>.
On Sun, May 07, 2006 at 11:03:02AM -0400, Andrus Adamchik wrote:
> Migration is successfully completed. Check ins can resume to the new
> location at https://svn.apache.org/repos/asf/incubator/cayenne/main/
> trunk/cayenne/
I've enabled the JIRA Subversion integration. Eg:
http://issues.apache.org/cayenne/browse/CAY-261?page=all
http://issues.apache.org/cayenne/browse/CAY-470?page=all
http://issues.apache.org/cayenne/browse/CAY-207?page=all
There are plenty of examples, as Andrus has been very good about
recording issue keys in commits.
--Jeff
> Andrus
>
>
> On May 6, 2006, at 4:12 PM, Andrus Adamchik wrote:
>
> > I am migrating CVS now. Do not check in code until further notice.
> >
> > As the CVS tarball from SF is old, I'll do a local merge of the
> > HEAD code into it. The worst scenario - we'll loose the last Beta
> > tag - no big deal. I recently did this operation with WOProject CVS
> > - it worked pretty well.
> >
> > Andrus
> >
> >
> > On May 5, 2006, at 1:47 PM, Cris Daniluk wrote:
> >
> >> My favorite part of SVN is the fact that the repository can easily
> >> evolve... directories are not only movable, but revision history is
> >> preserved. We can just branch when we're ready and change like crazy.
> >>
> >> I'm definitely +1
> >>
> >> On 5/5/06, Andrus Adamchik <an...@objectstyle.org> wrote:
> >>> Anonymous CVS @SF has been down since March. A number of users have
> >>> been complaining that they can't create patches or test their custom
> >>> changes because of that. The situation is not critical, but still
> >>> rather annoying.
> >>>
> >>> I am thinking maybe we should change our earlier decision to keep
> >>> 1.2
> >>> on SF and move it to Apache SVN now (but of course still keep doing
> >>> releases from SF with the current package naming)?
> >>>
> >>> Andrus
> >>>
> >>
> >
> >
[DONE] Re: Do not check in code until further notice
Posted by Andrus Adamchik <an...@objectstyle.org>.
Migration is successfully completed. Check ins can resume to the new
location at https://svn.apache.org/repos/asf/incubator/cayenne/main/
trunk/cayenne/
Andrus
On May 6, 2006, at 4:12 PM, Andrus Adamchik wrote:
> I am migrating CVS now. Do not check in code until further notice.
>
> As the CVS tarball from SF is old, I'll do a local merge of the
> HEAD code into it. The worst scenario - we'll loose the last Beta
> tag - no big deal. I recently did this operation with WOProject CVS
> - it worked pretty well.
>
> Andrus
>
>
> On May 5, 2006, at 1:47 PM, Cris Daniluk wrote:
>
>> My favorite part of SVN is the fact that the repository can easily
>> evolve... directories are not only movable, but revision history is
>> preserved. We can just branch when we're ready and change like crazy.
>>
>> I'm definitely +1
>>
>> On 5/5/06, Andrus Adamchik <an...@objectstyle.org> wrote:
>>> Anonymous CVS @SF has been down since March. A number of users have
>>> been complaining that they can't create patches or test their custom
>>> changes because of that. The situation is not critical, but still
>>> rather annoying.
>>>
>>> I am thinking maybe we should change our earlier decision to keep
>>> 1.2
>>> on SF and move it to Apache SVN now (but of course still keep doing
>>> releases from SF with the current package naming)?
>>>
>>> Andrus
>>>
>>
>
>
Do not check in code until further notice
Posted by Andrus Adamchik <an...@objectstyle.org>.
I am migrating CVS now. Do not check in code until further notice.
As the CVS tarball from SF is old, I'll do a local merge of the HEAD
code into it. The worst scenario - we'll loose the last Beta tag - no
big deal. I recently did this operation with WOProject CVS - it
worked pretty well.
Andrus
On May 5, 2006, at 1:47 PM, Cris Daniluk wrote:
> My favorite part of SVN is the fact that the repository can easily
> evolve... directories are not only movable, but revision history is
> preserved. We can just branch when we're ready and change like crazy.
>
> I'm definitely +1
>
> On 5/5/06, Andrus Adamchik <an...@objectstyle.org> wrote:
>> Anonymous CVS @SF has been down since March. A number of users have
>> been complaining that they can't create patches or test their custom
>> changes because of that. The situation is not critical, but still
>> rather annoying.
>>
>> I am thinking maybe we should change our earlier decision to keep 1.2
>> on SF and move it to Apache SVN now (but of course still keep doing
>> releases from SF with the current package naming)?
>>
>> Andrus
>>
>
Re: CVS migration to apache??
Posted by Cris Daniluk <cr...@gmail.com>.
My favorite part of SVN is the fact that the repository can easily
evolve... directories are not only movable, but revision history is
preserved. We can just branch when we're ready and change like crazy.
I'm definitely +1
On 5/5/06, Andrus Adamchik <an...@objectstyle.org> wrote:
> Anonymous CVS @SF has been down since March. A number of users have
> been complaining that they can't create patches or test their custom
> changes because of that. The situation is not critical, but still
> rather annoying.
>
> I am thinking maybe we should change our earlier decision to keep 1.2
> on SF and move it to Apache SVN now (but of course still keep doing
> releases from SF with the current package naming)?
>
> Andrus
>