* Glynn Foster <[EMAIL PROTECTED]> [2005-10-05 16:19]:
> Hey,
>
> On Wed, 2005-10-05 at 16:04 -0700, Mike Kupfer wrote:
> > >>>>> "Glynn" == Glynn Foster <[EMAIL PROTECTED]> writes:
> >
> > Glynn> I guess there's a 2 step migration of ON being planned - first to
> > Glynn> a centralized repository, and then adding the distributed element
> > Glynn> after that?
> >
> > No, just one migration. The plan is for ON to provide a one-way gateway
> > to a read-only Subversion repository.
>
> So, that sounds like it's only a half step towards moving to Subversion
> full time - but you comment is a little sparse on details so I could
> have completely misunderstood what you were suggesting.
>
> Does anyone have a good technical writeup of what is being planned -
> mostly because other consolidations are likely to be effected as well,
> and it would be good to have some heads up so we can work on a good
> migration story.
The previous summary* I thought precise, but I suppose that's suspect:
2. Source code management, first phase.
The Code Manager ("TeamWare") distributed source code manager
(SCM) has been in use at Sun for over twelve years; its
predecessors were also distributed SCM solutions. It is
difficult to envision how we might move the current practices of
the consolidations using TeamWare to an SCM that doesn't match up
well with the features and extensions that have been in use for
so long. However, TeamWare itself has deficits when we consider
its use on the open Internet (and even within Sun's wide area
network).
In order to make progress, and in order to support new and
current projects and consolidations that are not tied to
TeamWare, I believe that we must offer a centralized SCM facility
while the current set of open source distributed SCM solutions
are evaluated against criteria based on TeamWare's use within Sun
and on suitability for use on an Internet-hosted site. Luckily,
recent developments in the SCM space suggest that one or more
SCMs may meet many of these criteria already. A draft set of
criteria will be published shortly, after which candidate SCMs
will be evaluated against them.
The proposed centralized SCM solution is Subversion, based on
features, ease of integration, and community vigor. Information
on Subversion may be found at
http://subversion.tigris.org/
Tools to make the source drops of TeamWare-based consolidations
available via a read-only repository will also be
found/refined/developed. We will publish a representation of ON
via a read-only repository during this phase.
That is, if a consolidation wants centralized SCM access, then it will
be able to use Subversion, once the site support has been implemented.
If a consolidation wants distributed SCM, then it has to wait for an
evaluation phase to complete, and then for the implementation of site
support. Thus, migration issues can only be currently engaged with by
consolidations that believe the centralized facility is sufficient for
their needs.
Basic project hosting will be implemented first.
- Stephen
* http://www.opensolaris.org/jive/thread.jspa?threadID=2174
--
Stephen Hahn, PhD Solaris Kernel Development, Sun Microsystems
[EMAIL PROTECTED] http://blogs.sun.com/sch/
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
