[loki-editor commit] r679 - wiki
codesite...@google.com
Date: Tue Dec 30 11:42:42 2008
New Revision: 679
Modified:
wiki/Releasing.wiki
Log:
Edited wiki page through web user interface.
Modified: wiki/Releasing.wiki
==============================================================================
--- wiki/Releasing.wiki (original)
+++ wiki/Releasing.wiki Tue Dec 30 11:42:42 2008
@@ -4,10 +4,9 @@
Packaging and releasing Loki is a simple process, but many of its steps
are easy to forget. Following this list will ensure that you remember all
of them.
# Update the [Changelog changelog] to reflect the new changes that have
been made since the last release.
- # Build the Loki tarballs and place them in the `packaging` directory on
the testbed. You can do this by changing to the packaging directory, and
then running `../branches/2.x/tools/build -v [version] --with-source`.
- # Extract the general-use tarball you just created into the `releases`
directory.
+ # Build the Loki tarballs on the testbed by running `./build 2.0
[version]` in the root `loki2` directory.
# In multiple browsers, do one last check to ensure that all changes are
still working, and run the [http://jscrucible.googlecode.com/ Crucible]
tests.
- # Tag the release as _release-`version`_ in Subversion.
+ # Tag the release as _release-`version`_ in Git. (`git tag -s
release-[version]`)
# Upload the general-use and source tarballs to Google Code. Label the
new general-use tarball as _Featured_ and, if this release immediately
supersedes an earlier one, mark the older tarballs as _Deprecated_.
# Post a release announcement to the
[http://groups.google.com/group/loki-installers Loki installers mailing
list].
# Add a _Fixed-`version`_ label to the issue tracker for the next
version after the one you've just released.