Noah,
> >
> > Question: will it do any good to upload the polaris-20061002
> > tree into our subversion repository as another branch ?
> braching will always create problem of merging. why not aligh with sun
> lab's efforts and start it as main trunk? in this stage, the fastest
> way to make the development move forward is to work from the same
> source base.
Ok, I'll try to elaborate more on that.
First of all I agree that we need to continue from the sunlabs sources.
As a matter of fact we have no other source base today that runs,
so no doubts here.
So, no.1 - use polaris-20061002 tarball as a starting point.
No. 2 - the source needs to be in some SCM (even for single developer,
let alone community).
Ok, among great variety of the SCM we can realistically choose between
two systems - Subversion and Mercurial.
Subversion is ok, but only as a short-term solution. It is easy to import
polaris-20061002 into trunk and continue from there, but it has two
little "buts"
1. I am not sure SunLabs would use it - they refused to use it before.
(I mean the repo at svn.genunix.org)
2. ON going to switch to Mercurial. And it makes great sense to stick
to the same SCM as our upstream. Otherwise merges will become
a nightmare.
Mercurial is excellent. However, for this to be done right our repo
should be a child of the upstream ON repo. And to work with such
a repo polaris changes should be a set of deltas against the
upstream repo.
If you/anyone see any better way, please speak up !
--
Regards,
Cyril
