>
> main branch:
> /trunk/harbour (what we have)
>
> bugfix branches:
> /branches/harbour-1.0
> /branches/harbour-1.1
> /branches/harbour-2.0
>
> read-only "tags":
> /tags/harbour-1.0.0RCn
> /tags/harbour-1.1.0bn
> /tags/harbour-1.1.0RCn
> /tags/harbour-2.0.0bn
> /tags/harbour-2.0.0RCn
> (we already have all the old CVS "tags" here)
>
> Opinions? Phil?
>
> Brgds,
> Viktor
>
This is the correct and expected svn organization.
Making subdirectories for releases in the trunk is confusing, and out of
subversion standards.
This makes standard source code operations ("merging from trunk", "taking diffs
between releases") difficult or impossible.
Many other tools expects organization like above.
We use internally git scm infrastructure, and pull harbour via git-svn. For
that tool is expected to have /trunk, /branches/, /tags/ organization like
proposed in Viktor's post.
Regards,
Ernad
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
