db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "ReleaseNoteProcess" by KristianWaagan
Date Thu, 17 Jan 2013 09:56:10 GMT
Dear Wiki user,

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

The "ReleaseNoteProcess" page has been changed by KristianWaagan:
http://wiki.apache.org/db-derby/ReleaseNoteProcess?action=diff&rev1=21&rev2=22

      -Djira.user=<jira user name>
      -Djira.password=<password for that user>
      -Drelease.version=<version of the release in JIRA>
-     -Djira.filter.id=<id of the search filter>
     genrelnotes
  }}}
  
  If you forget or have not set any of these settings, the release notes build will fail and
you will be informed of which element you've missed.
  
- To find the jira filter id, I saved the JIRA query as a filter, and then used the number
following the id in the url window when the search was issued.
+ By default the tool will use JQL to query JIRA. If the query fails for some reason, you
can create you own custom filter in JIRA and point the tool at it by specifying `jira.filter.id`.
To find the filter id, save the JIRA query as a filter, and then use the number following
the id in the url window when the search has been issued.
+ 
+ You can also specify `reportDisqualifications=true` to see the issues that are disqualified.
Currently, the only cause for a disqualification is that the fix for an issue has already
been included in a previous version in the ancestry chain.
  
  Depending on the size of the reports to handle, you may need to set `ANT_OPTS`, for instance
to `-Xms100m -Xmx200m`. You may obviously also put `relnotes.src.reports` in `ant.properties`
if you prefer.
  
- Please note that the Release Manager should run the JIRA report to generate `fixedBugsList.xml`
freshly just before typing `ant genrelnotes`. This is because, during the release period,
new issues may be fixed and included in the release and the text for individual release notes
may be improved. Stale reports overlook the new issues and improved notes.
- 
  On Windows when you try to commit you may get the message <code> svn: Inconsistent
line ending style </code>. To resolve this Kathey went into emacs and removed the ^M's.
Myrna's solution was to install cygwin's dos2unix & unix2dos and use them in sequence.
Lily's solution is run perl command "perl -p -e 's/\r$//' < RELEASE-NOTES.html > ~/RELEASE-NOTES.html
  

Mime
View raw message