SVN repository up and running

[Luke Maurits]

Hi prettytable-devel,

After releasing PrettyTable 0.5 a short while ago, I have now set up
the project's SVN repository. The repo structure and development
process is fairly typical:

* Ongoing work will happen in "trunk"
* As we approach release time, "trunk" will be branched into, e.g.,
"branches/0.6"
* "branches/0.6" will be tagged into "tags/0.6-RC1" - this release
candidate will be downloaded and tested by users.
* Fixes to problems found during testing of 0.6-RC1 will be done in
"branches/0.6" (and also in trunk), which will be tagged again after
significant work as 0.6-RC2, then 0.6-RC3, etc until there appear to
be no more problems.
* When everything is ready for release, "branches/0.6" will be tagged
into "tags/0.6-RELEASE".
* New major work happens in "trunk" which is eventually branched into
"branches/0.7" and the cycle repeats.

You can see an example process in the current repo (see branches/0.5
and tags/0.5-RELEASE).

Please note that you won't be able to commit to the repository without
first becoming a member of the PrettyTable project in Google code -
this is different from subscribing to any of the lists. Project
membership is extended on an invite basis, not a request basis (this
is enforced by Google code, not my choice). If anybody wants to
become a member so they can commit code, send me an email asking to be
invited. In general, I will invite people to become project members
with commit rights only after they have demonstrated their good
intentions and Python proficiency by emailing fixes either to me or to
this list.

Of course, anybody is free, member or not, to make a read-only
checkout of the repository at any time.

Soon I will begin working in trunk on PrettyTable 0.6, which will be
an API-tidy up release. I'll make a separate post to the devel group
shortly explaining what's in store for 0.6 and asking for advice, etc.

If anybody has any questions about the SVN repository, feel free to
reply to this post.

Luke