Re: [Openslp-devel] SourceForge.net site update in progress...

[Nick W. <ne...@wi...>]

I used git a little bit, but I haven't really used a DVCS professionally.
 +1 for either git or mercurial.


On Wed, Nov 14, 2012 at 12:12 PM, John Calcote <joh...@gm...>wrote:

> OpenSLP developers,****
>
> ** **
>
> I have two issues to bring up this morning.****
>
> ** **
>
> *OpenSLP Site Update*
>
> ** **
>
> While out on sf.net today, I noticed that there was a site update
> available to which project admins must “opt in”. I carefully read the
> documentation about the update to ensure that it would have no negative
> impact on our project or developers, but apparently I missed the part where
> the repositories are updated to new locations and directory structures.
> Thus (and I apologize for any inconvenience this may cause) you will need
> to check out a new work area using the new svn repository locations before
> committing any more work to the repo. You can find the new repo locations
> listed on this page:****
>
> ** **
>
>     https://sourceforge.net/p/openslp/code/****
>
> ** **
>
> Click the “RW” button to ensure you’re using the URL that will grant you
> read/write access. The new location follows this pattern (where sfuserid is
> your sourceforge user id):****
>
> ** **
>
>     ssh://sfu...@sv.../p/openslp/code/trunk openslp-code****
>
> ** **
>
> Thus, you can use the following command to get your new work area:****
>
> ** **
>
>     svn checkout --username=sfuserid svn+ssh://
> sfu...@sv.../p/openslp/code/trunk openslp-code****
>
> ** **
>
> The repo is currently updating, so please wait till the import has
> completed before checking out your new work areas. The import status is
> available at the top of the page on the link above.****
>
> ** **
>
> *Distributed Version Control*
>
> ** **
>
> Now on to the next topic: I’m considering switching to a distributed
> version control system (DVCS) like git or mercurial. These tools are nearly
> identical, so I’m not particularly concerned which one we use, but since
> I’ve started using a DVCS professionally a couple of years ago, I’ve begun
> to wonder why anyone stays with centralized VCS systems like CVS or
> Subversion anymore. The mercurial patch queue features alone are worth the
> switch. ****
>
> ** **
>
> My only concern, at this point, is that some of you may not be familiar or
> comfortable with DVCS’s because your work experience hasn’t taken you in
> that direction yet. So I’ll leave it up to you – let’s take a vote and see
> if we’re willing and able to switch over to a DVCS, and which one we would
> prefer. My vote is:****
>
> ** **
>
>     +1/mercurial****
>
> ** **
>
> I have to tell you that, while I don’t mind using git, there are a couple
> of reasons I prefer mercurial: 1) I’ve been using mercurial so I understand
> it completely, and 2) mercurial is written in python, so it has none of the
> (Windows) portability issues associated with git (Cygwin/msys, etc).****
>
> ** **
>
> John****
>
> ** **
>
>
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> _______________________________________________
> Openslp-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openslp-devel
>
>