aboutsummaryrefslogtreecommitdiff
path: root/readme.txt
diff options
context:
space:
mode:
authorJon Skeet <skeet@pobox.com>2010-04-01 20:32:45 +0100
committerunknown <Jon@.(none)>2010-04-01 20:32:45 +0100
commitae9b3ff224eb251674584e8e414010d2d0ed2cb1 (patch)
tree876497e16a500a17c0cae7755c1afabfa5d0b265 /readme.txt
parentd3f2d098fa39596bf6ea59bb93d485e8aaaf7476 (diff)
downloadprotobuf-ae9b3ff224eb251674584e8e414010d2d0ed2cb1.tar.gz
protobuf-ae9b3ff224eb251674584e8e414010d2d0ed2cb1.tar.bz2
protobuf-ae9b3ff224eb251674584e8e414010d2d0ed2cb1.zip
Release preparation
Diffstat (limited to 'readme.txt')
-rw-r--r--readme.txt31
1 files changed, 30 insertions, 1 deletions
diff --git a/readme.txt b/readme.txt
index 0ffdc7cf..85142a61 100644
--- a/readme.txt
+++ b/readme.txt
@@ -1 +1,30 @@
-Welcome! This is, of course, a placeholder file. \ No newline at end of file
+Welcome to the C# port of Google Protocol Buffers, written by Jon Skeet
+(skeet@pobox.com) based on the work of many talented people.
+
+For more information about this port, visit its homepage:
+http://protobuf-csharp-port.googlecode.com
+
+For more information about Protocol Buffers in general, visit the
+project page for the C++, Java and Python project:
+http://protobuf.googlecode.com
+
+
+Release 0.9
+-----------
+
+Due to popular demand, I have built a version of the binaries to put
+on the web site. Currently these are set at assembly version 0.9,
+and an assembly file version of 0.9. This should be seen as a mark
+of the readiness of the release process more than the stability of
+the code. As far as I'm aware, the code itself is perfectly fine: I
+certainly have plans for more features particularly around making
+code generation simpler, but you should feel confident about the
+parsing and serialization of messages produced with this version of
+the library. Of course, if you do find any problems, *please* report
+them at the web site.
+
+Currently the downloadable release is built with the snk file which
+is in the open source library. I am considering having a privately
+held key so that you can check that you're building against a
+"blessed" release - feedback on this (and any other aspect of the
+release process) is very welcome.