Nut upsdev - Feb 2013 - Alioth Subversion repository freeze

Dear developers,

thanks to Charles (Lepple) and ESR hard work, we are now able to finalize
our migration from Subversion to Git, on Alioth.

As of now, our Subversion repository on
Alioth<https://alioth.debian.org/scm/?group_id=30602>is FROZEN!
Any new svn commit may simply be discarded, so beware!

Most active developers are currently using github, as a temporary mean.
But if you have any issue, contact us back by replying to this mail.

Stay tuned for the come back.

(details)
This move represents more than a couple of years of investigations and
testing from Charles!
The constraints are:
- no loss of any bit of our source code history,
- adapt meta information and history to fit git approach, and fit the point
above.

As for the documentation revamp and Asciidoc, the solution came from Eric:
his tool (reposurgeon <https://gitorious.org/reposurgeon>) found a good
testbed
for improvements with NUT
<https://gitorious.org/reposurgeon/nut-conversion>,
over the past year.
and Charles has been an ideal partner for working on these improvements
(quoting Eric).
Thanks again Charles and Eric!

In the end, Free and Opensource Software get better, and that's why
we're
all here ;-)

cheers,
Arnaud
-- 
NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20130206/b558425c/attachment.html>

Thank you for your patience while we migrated the NUT repository to Git.

We have a "networkupstools" organization set up on Github, and the
main Git repository is hosted there:

   https://github.com/networkupstools/nut

Feel free to fork, submit pull requests, and file issues there. If you had SVN
commit access at Alioth, email me (or Arnaud) your Github user ID, and we'll
add you to the organization.

$ git clone git://github.com/networkupstools/nut.git

 - * - * - * -

The Alioth site will function as a backup:

   https://alioth.debian.org/scm/browser.php?group_id=30602

(All of the existing issue trackers are still active at Alioth.)

If you want to see just about every single branch and tag that we ever had in
CVS or SVN, here is the entire output of reposurgeon:

   https://github.com/networkupstools/nut-archive

I will also keep the old Trac instance up for a while, for cross-referencing SVN
revisions:

   http://trac.networkupstools.org/projects/nut/timeline

 - * - * - * -

The NUT documentation still needs to be updated to reflect the new repository
and development methods. Please email nut-upsdev if you have specific changes to
suggest (bonus points if you have a ready-to-apply patch).

 - * - * - * -

I also need to update the NUT Buildbot configuration to pull from Git. If you
maintain a buildslave, please check to ensure that the Git package for your OS
is installed.

 - * - * - * -

If you forked my experimental Github tree (based on git-svn) originally located
at https://github.com/clepple/nut, note that it has been renamed to
https://github.com/clepple/nut-git-svn .

Be aware that the reposurgeon conversion improved a lot of the old commit
messages, and as such, branches derived from the git-svn conversion (including
pretty much anything currently in https://github.com/balooloo/nut ) will need to
be rebased before they are merged back into the main NUT repository. Details
will vary. Email me on nut-upsdev and I'll explain.

 - * - * - * -

None of this would have been possible without the tenacity of ESR while
upgrading reposurgeon to better handle Subversion repositories (especially tough
cases like ours, which had some interesting corner cases due to its roots in a
cvs2svn conversion). In the end, his repodiffer tool gave us the warm fuzzy
feeling that everything had been properly converted, and it even pointed out
some bugs in git-svn, as well as the SVN documentation itself.

The main reposurgeon web site is:

   http://www.catb.org/~esr/reposurgeon/

The fork of reposurgeon that we used (only a few commits beyond v2.20) is:

   https://gitorious.org/~clepple/reposurgeon/clepple-reposurgeon (nut-extras
branch)

The metadata used to refine the CVS/SVN commit messages and the Git revision
topology:

   https://gitorious.org/~clepple/reposurgeon/clepple-nut-conversion (nut-extras
branch)

-- 
Charles Lepple
clepple at gmail