Re: create a release-0.22 branch now ?

> although i would prefer to name it 
> 
>     http://project.tigris.org/svn/scarab/branches/0.22-RC
> 
> [snip]
> 
> and finally:
> 
>   http://project.tigris.org/svn/scarab/tags/release/SCARAB-0.22

Using the subfolder /releases/ i have no objection to.

But the whole renaming from 0.22-RC to 0.22 i don't see any point.
Both are not going to exist at the same time so for the purpose of the
repository there's no need to distinguish, it's just another job (albeit
shorter than writing this email - but developers can be confused when
the branch they are working on "disappears"!).
Making the distinguish that the branch is now a final release (although
i don't believe any such thing truly ever exists for any version) is a
job for the website, wiki, and|or download page.

~mck

-- 
"Although the Buddhists will tell you that desire is the root of
suffering, my personal experience leads me to point the finger at system
administration." Philip Greenspun 
| semb.wever.org | sesat.no | sesam.no |

------------------------------------------------------
http://scarab.tigris.org/ds/viewMessage.do?dsForumId=455&dsMessageId=1014042

To unsubscribe from this discussion, e-mail: [[email protected]].

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAklngYcACgkQkdPrePiuutMoZQCgwa2JgMAhIhRgSW6NsIkJ9drS
XewAoK+R9Gfb1xY0ZGMb091lDP5TeXrz
=NtS+
-----END PGP SIGNATURE-----