[eclipse.org-architecture-council] [Bug 249745] New: Eclipse Repository

[bugzilla-daemon@xxxxxxxxxxx]

https://bugs.eclipse.org/bugs/show_bug.cgi?id=249745  
Product/Component: Community / Architecture Council
           Summary: Eclipse Repository Best Practices
           Product: Community
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Architecture Council
        AssignedTo: eclipse.org-architecture-council@xxxxxxxxxxx
        ReportedBy: martin.oberhuber@xxxxxxxxxxxxx


Starting from some installation problems with Subversive, a discussion broke
out on the eclipse.org-committers mailing list about pros and cons of various
CM systems and their integrations into Eclipse. Here is one of the newer
postings in that thread:

  http://dev.eclipse.org/mhonarc/lists/eclipse.org-committers/msg00653.html

Since it's on the EAC's charter to recommend Best Practices and articulate the
pros and cons of various solutions on behalf of the projects, I'd like to
continue the discussions here. As we are gathering knowledge (and hopefully
some consensus), these discussions should eventually be combined into a Wiki
page.

Here is some of the current thoughts as a seed:

* CVS
  + Most mature integration into Eclipse
  + Readily usable by headless PDE basebuilder
  + Simple and proven Repository maintenance (filesystem-based)
  - Cannot track moves and renames (merge issues when branches deviate)
  - Requires SSH to get through a firewall

* SVN
  + Tracks moves and renames
  + Allows http / https only Repository access
  - No consensus yet on Eclipse Integrations (Subversive vs. Subclipse)
  - Clients perceived much slower than CVS
  - Problematic Repository maintenance (database-based)

* Git
  + Distributed Repository architecture, very fast
  + Good at merging branches even if they deviate
  - Good on Linux, problematic on Windows

* Others?

I'd like to see the discussion focused on technical facts (X is good because...
Y is problematic because...) as well as actionable items (we could Z... we
should investigate XX...) and pointers / hyperlinks to additional information
as well as real use-cases stories ("We've been using KK since ... and it worked
well for use because...)

This is *not* the place for
* Rants that nobody gains anything from
* Bug reports against any tool (file a bug against subversive / subclipse / xx
  and add a hyperlink here instead)

Let's see where this brings us!


-- 
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.