lucene-java-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Lucene-java Wiki] Update of "ReleaseTodo" by MikeMcCandless
Date Fri, 03 Oct 2008 16:45:30 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucene-java Wiki" for change notification.

The following page has been changed by MikeMcCandless:
http://wiki.apache.org/lucene-java/ReleaseTodo

The comment on the change is:
Add "update versions in website tabs.xml/index.xml" early in the process

------------------------------------------------------------------------------
  }}}
     1. After branching the new release series, update the default version in common-build.xml
on trunk to X.Y+1-dev and the default version in common-build.xml on the branch to X.Y (remove
the -dev suffix).
     1. Update CHANGES.txt and contrib/CHANGES.txt in trunk and the branch. Specify tentative
release date and start a new section for X.Y+1-dev in the trunk's CHANGES.txt.
+    1. On trunk, fix src/site//src/documentation/content/xdocs/{tabs.xml,index.xml} to reference
the X.Y+1-dev version.  Rebuild the website (http://wiki.apache.org/lucene-java/HowToUpdateTheWebsite)
and commit.
+    1. On the branch, fix the same files, rebuild the website and commit.
     1. Send a note to java-dev to inform the committers that the branch has been created
and the feature freeze phase has started. Include Do's and Don'ts for the feature freeze phase:
        * No new features may be committed to the branch.
        * Documentation patches, build patches and serious bug fixes may be committed to the
branch. However, you should submit *all* patches you want to commit to Jira first to give
others the chance to review and possibly vote against the patch. Keep in mind that it is our
main intention to keep the branch as stable as possible.

Mime
View raw message