wxcode-users

[wxCode-users] Moving wxCode components from CVS to SVN?

[Ulrich T. <ulr...@gm...>]

Probably most of you already know that SourceForge's servers were
attacked last week
(http://sourceforge.net/blog/sourceforge-attack-full-report/). Several
SF services are still down, among them CVS hosting, shell and project
website access and browsing repositories.

In the report is mentioned that SF considers to end CVS service,
although this is heavily disputed in the comments. Nevertheless this
made me think about the current situation of the wxCode project:

About one half of the wxCode components is hosted in CVS, the other half
in SVN. This makes it a bit complicated to use and administer the
components. Personally I would prefer to have all components in one
repository only.

Maybe SourceForge forces us to perform the transition from CVS to SVN,
maybe not. Indepently of SourceForge's decision I'd like to get opinions
from the wxCode developers whether we should make nevertheless the
transition and host *all* components in SVN.

Regards,

Ulrich

Re: [wxCode-users] Moving wxCode components from CVS to SVN?

[Francesco <f18...@ya...>]

Hi Ulrich,
yes, I think that nowadays CVS is used only by a small number of projects...
the big part I think has moved to SVN (which btw has a lot of advantages).
I think that just asking on the mailing list is the best idea. I remember
that John was still not used to SVN say 1/2 years ago but now probably
things have changed!

For me, obviously is ok (and all my components should already be in the SVN
repo)

Thanks!
Francesco

2011/1/31 Ulrich Telle <ulr...@gm...>

> Probably most of you already know that SourceForge's servers were
> attacked last week
> (http://sourceforge.net/blog/sourceforge-attack-full-report/). Several
> SF services are still down, among them CVS hosting, shell and project
> website access and browsing repositories.
>
> In the report is mentioned that SF considers to end CVS service,
> although this is heavily disputed in the comments. Nevertheless this
> made me think about the current situation of the wxCode project:
>
> About one half of the wxCode components is hosted in CVS, the other half
> in SVN. This makes it a bit complicated to use and administer the
> components. Personally I would prefer to have all components in one
> repository only.
>
> Maybe SourceForge forces us to perform the transition from CVS to SVN,
> maybe not. Indepently of SourceForge's decision I'd like to get opinions
> from the wxCode developers whether we should make nevertheless the
> transition and host *all* components in SVN.
>
> Regards,
>
> Ulrich
>
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better
> price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
>

Re: [wxCode-users] Moving wxCode components from CVS to SVN?

[PGridDev <pgr...@ya...>]

Hi Ulrich, Francesco & all  --I'll take this as a request for comments!

I am pro-Subversion (for me an obvious improvement), although my component is still under CVS. I also agree that having 2 different repositories makes little sense other than during a transition phase.

My only objection / concern is with history: components under CVS are logically the older ones, and in some cases (like mine) were inherited from other developers. The comments in CVS (assuming our predecessors have commited with comments) are sometimes the only information available as to why something was implemented in a certain way.

Therefore I am in favor of a migration CVS ==> SVN which ideally includes migrating history, at least in a dedicated branch; obviously more effort, and I have never done it myself.
Now, to be honest, I had to go through the comments & history only once...

Happy to let you & the rest of the wxCode community decide, this was just some input.

Cheers,
Ronan


On 01/02/2011 00:14, Francesco wrote:
> Hi Ulrich,
> yes, I think that nowadays CVS is used only by a small number of projects... the big part I think has moved to SVN (which btw has a lot of advantages).
> I think that just asking on the mailing list is the best idea. I remember that John was still not used to SVN say 1/2 years ago but now probably things have changed!
>
> For me, obviously is ok (and all my components should already be in the SVN repo)
>
> Thanks!
> Francesco
>
> 2011/1/31 Ulrich Telle <ulr...@gm... <mailto:ulr...@gm...>>
>
>     Probably most of you already know that SourceForge's servers were
>     attacked last week
>     (http://sourceforge.net/blog/sourceforge-attack-full-report/). Several
>     SF services are still down, among them CVS hosting, shell and project
>     website access and browsing repositories.
>
>     In the report is mentioned that SF considers to end CVS service,
>     although this is heavily disputed in the comments. Nevertheless this
>     made me think about the current situation of the wxCode project:
>
>     About one half of the wxCode components is hosted in CVS, the other half
>     in SVN. This makes it a bit complicated to use and administer the
>     components. Personally I would prefer to have all components in one
>     repository only.
>
>     Maybe SourceForge forces us to perform the transition from CVS to SVN,
>     maybe not. Indepently of SourceForge's decision I'd like to get opinions
>     from the wxCode developers whether we should make nevertheless the
>     transition and host *all* components in SVN.
>
>     Regards,
>
>     Ulrich
>
>
>     ------------------------------------------------------------------------------
>     Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
>     Finally, a world-class log management solution at an even better price-free!
>     Download using promo code Free_Logger_4_Dev2Dev. Offer expires
>     February 28th, so secure your free ArcSight Logger TODAY!
>     http://p.sf.net/sfu/arcsight-sfd2d
>     _______________________________________________
>     wxCode-users mailing list
>     wxC...@li... <mailto:wxC...@li...>
>     https://lists.sourceforge.net/lists/listinfo/wxcode-users
>
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
>
>
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users

Re: [wxCode-users] Moving wxCode components from CVS to SVN?

[Ulrich T. <ulr...@gm...>]

Hi Ronan,

> I am pro-Subversion (for me an obvious improvement), although my
> component is still under CVS. I also agree that having 2 different
> repositories makes little sense other than during a transition phase.

... and this transition phase lasted already several years (Francesco
introduced SVN to wxCode years ago). Now there are even developers
favoring Git or Mercurial above SVN.

> My only objection / concern is with history: components under CVS are
> logically the older ones, and in some cases (like mine) were inherited
> from other developers. The comments in CVS (assuming our predecessors
> have commited with comments) are sometimes the only information
> available as to why something was implemented in a certain way.
> 
> Therefore I am in favor of a migration CVS ==> SVN which ideally
> includes migrating history, at least in a dedicated branch; obviously
> more effort, and I have never done it myself.

Neither have I, but there is a tool cvs2svn which is said to support
migration including history. I'll have to dig through the documentation
to find out which steps are required to move components separately from
CVS to SVN without damaging the SVN repository.

> Happy to let you & the rest of the wxCode community decide, this was
> just some input.

I think I can at least move all currently unmaintained components. But
this has to wait until SourceForge's services are available again. I'll
announce on this list when I prepare the migration.

Regards,

Ulrich

Re: [wxCode-users] Moving wxCode components from CVS to SVN?

[Ulrich T. <ulr...@gm...>]

Hi Francesco,

> yes, I think that nowadays CVS is used only by a small number of projects...
> the big part I think has moved to SVN (which btw has a lot of advantages).

I agree. I was very happy when you introduced SVN to wxCode years ago.

> I think that just asking on the mailing list is the best idea. I remember
> that John was still not used to SVN say 1/2 years ago but now probably
> things have changed!

I'm going to contact all developers which still maintain wxCode
components in CVS by mail, since I don't know whether all of them follow
this list.

Currently SourceForge's services are still down, so nothing is going to
change soon.

Regards,

Ulrich