Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Swordfish:Project Rules"

(Internal IP Compliance Guidelines)
 
(14 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Methodology ==
+
== Methodology ==
Swordfish is developed using the [http://en.wikipedia.org/wiki/Scrum_(development) scrum method].
+
  
== Common definition of "Done" ==
+
Swordfish is developed using the [http://en.wikipedia.org/wiki/Scrum_(development) scrum method].  
We have a first draft [[Swordfish:ProjectRules:CoDoD | Common definition of "Done"]] to be discussed.
+
  
== Documentation Rules ==
+
== Common definition of "Done"  ==
* After creating new content in the Swordfish Wiki, contact the documentation folks to link your page appropriately.
+
* Ensure that you add a link back to the [[Swordfish | Swordfish Wiki Home]] at the end of every page.
+
  
== Release Checklist ==
+
We have a first draft [[Swordfish:ProjectRules:CoDoD|Common definition of "Done"]] to be discussed.
  
<p>Here is a list of the tasks that should be done on the last day of each sprint.</p>
+
== Documentation Rules  ==
<ul>
+
  <li>Check that the [[http://sop-bp02.servicebackbone.org:8080/dashboard/tab/build/detail/svn_org.eclipse.swordfish.tooling| CruiseControl]] build is fine and that the system tests are ok. </li>
+
  <li>Create a tag.</li>
+
  <li>Check out the tag into an empty directory.</li>
+
  <li>Run the Swordfish Tooling build and the </li>
+
  <li></li>
+
</ul>
+
  
 +
*After creating new content in the Swordfish Wiki, contact the documentation folks to link your page appropriately.
 +
*Ensure that you add a link back to the [[Swordfish|Swordfish Wiki Home]] at the end of every page.
  
1. Check that CruiseControl build is fine, as well as system tests were ok.
+
== Internal IP Compliance Guidelines  ==
2. Make a tag.  
+
We have a first draft [[Swordfish:ProjectRules:IPComplianceProcess_Internal|Internal IP Compliance Process]] to be discussed and reviewed by the team.
3. Checkout tag into empty directory.
+
12:34, 27 July 2009 (UTC)
4. Run tooling build, run systemtest build. Ensure builds are passed.
+
5. Execute Manual tests.
+
  
List of the Manual tests.
+
== Release Checklist  ==
  
1. Installing Target Platform
+
Here is a list of the tasks that should be done on the last day of each sprint.  
2. Installing BPEL Designer.
+
3. Check that BPEL project and BPEL process file are created without errors.
+
4. Check Welcome page:
+
- Overview page; click Swordfish link and make sure that link refers to Swordfish Help
+
- Tutorial page; click Swordfish links and make sure that links refer to Swordfish Cheatsheets
+
- Samples page; click Swordfish link and make sure that link refers to BPEL Sample
+
5. Run JAX-WS project.
+
6. Check Swordfish Eclipse Help.
+
7. Check context help for JAX-WS wizard.
+
  
 +
#Check that the [[http://sop-bp02.servicebackbone.org:8080/dashboard/tab/build/detail/svn_org.eclipse.swordfish.tooling| Swordfish Tooling]] build is fine in cruise control and that the [[http://sop-bp02.servicebackbone.org:8080/dashboard/tab/build/detail/svn_org.eclipse.swordfish.tooling.systemtest| System Test]]system tests are completed.
 +
#Create a tag.
 +
#Check out the tag into an empty directory.
 +
#Run the Swordfish Tooling build and the system test build.
 +
#Execute manual tests.
  
</pre>
+
These manual tests must be completed:
-------------------------------
+
 
[[Swordfish | Swordfish Wiki Home]]
+
#Install the Target Platform
 +
#Install BPEL Designer
 +
#Check that the BPEL project and the BPEL process files are created without errors.
 +
#Check the Eclipse IDE Welcome page
 +
 
 +
*Overview page; click '''Swordfish'''and make sure that link refers to Swordfish Help
 +
*Tutorial page; click on the link and check that it takes you to the Swordfish Cheat Sheets
 +
*Samples page; click on the link and check that it takes you the BPEL sample.
 +
 
 +
#Run JAX-WS project.
 +
#Check Swordfish Eclipse Help.
 +
#Check JAX-WS wizard's context sensitive help.
 +
 
 +
<br>  
 +
 
 +
<br>
 +
 
 +
----
 +
 
 +
[[Swordfish|Swordfish Wiki Home]]

Latest revision as of 08:34, 27 July 2009

Methodology

Swordfish is developed using the scrum method.

Common definition of "Done"

We have a first draft Common definition of "Done" to be discussed.

Documentation Rules

  • After creating new content in the Swordfish Wiki, contact the documentation folks to link your page appropriately.
  • Ensure that you add a link back to the Swordfish Wiki Home at the end of every page.

Internal IP Compliance Guidelines

We have a first draft Internal IP Compliance Process to be discussed and reviewed by the team. 12:34, 27 July 2009 (UTC)

Release Checklist

Here is a list of the tasks that should be done on the last day of each sprint.

  1. Check that the [Swordfish Tooling] build is fine in cruise control and that the [System Test]system tests are completed.
  2. Create a tag.
  3. Check out the tag into an empty directory.
  4. Run the Swordfish Tooling build and the system test build.
  5. Execute manual tests.

These manual tests must be completed:

  1. Install the Target Platform
  2. Install BPEL Designer
  3. Check that the BPEL project and the BPEL process files are created without errors.
  4. Check the Eclipse IDE Welcome page
  • Overview page; click Swordfishand make sure that link refers to Swordfish Help
  • Tutorial page; click on the link and check that it takes you to the Swordfish Cheat Sheets
  • Samples page; click on the link and check that it takes you the BPEL sample.
  1. Run JAX-WS project.
  2. Check Swordfish Eclipse Help.
  3. Check JAX-WS wizard's context sensitive help.




Swordfish Wiki Home

Back to the top