Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Jetty/Contributor/Bug Tracking"

m
m
Line 3: Line 3:
 
Currently the jetty @ eclipse project is using bugzilla without any integration with svn, thus some degree of convention is needed until such time as we can automate the system:
 
Currently the jetty @ eclipse project is using bugzilla without any integration with svn, thus some degree of convention is needed until such time as we can automate the system:
  
* Jetty 6 bugs should be raised/tracked in [[http://jira.codehaus.org/browse/JETTY JIRA at codehause]]
+
* Jetty 6 bugs should be raised/tracked in [http://jira.codehaus.org/browse/JETTY JIRA @ codehause]
* Jetty 7 bugs should be raised/tracked in [[http://bugs.eclipse.org/bugs/ Bugzilla at eclipse]] using project "RT" and product "Jetty"
+
* Jetty 7 bugs should be raised/tracked in [http://bugs.eclipse.org/bugs/ Bugzilla @ eclipse] using project "RT" and product "Jetty"
 
* Jetty 8 bugs should be handled the same a jetty-7 bugs.  Note that as jetty-7 is currently being regularly merged with Jetty-8, there is no need to replicate jetty-7 issues for jetty-8
 
* Jetty 8 bugs should be handled the same a jetty-7 bugs.  Note that as jetty-7 is currently being regularly merged with Jetty-8, there is no need to replicate jetty-7 issues for jetty-8
 
* The VERSION.txt and commit messages for changes should include the bugzilla issue number
 
* The VERSION.txt and commit messages for changes should include the bugzilla issue number
 
* When a bugzilla issue is marked as fixed, the SVN r numbers should be added as a comment
 
* When a bugzilla issue is marked as fixed, the SVN r numbers should be added as a comment

Revision as of 20:12, 5 April 2009

Jetty Bug Tracking

Currently the jetty @ eclipse project is using bugzilla without any integration with svn, thus some degree of convention is needed until such time as we can automate the system:

  • Jetty 6 bugs should be raised/tracked in JIRA @ codehause
  • Jetty 7 bugs should be raised/tracked in Bugzilla @ eclipse using project "RT" and product "Jetty"
  • Jetty 8 bugs should be handled the same a jetty-7 bugs. Note that as jetty-7 is currently being regularly merged with Jetty-8, there is no need to replicate jetty-7 issues for jetty-8
  • The VERSION.txt and commit messages for changes should include the bugzilla issue number
  • When a bugzilla issue is marked as fixed, the SVN r numbers should be added as a comment

Back to the top