Difference between revisions of "Swordfish:Project Rules"

From Eclipsepedia

Jump to: navigation, search
(Internal IP Compliance Guidelines)
 
(6 intermediate revisions by one user not shown)
Line 13: Line 13:
  
 
== Internal IP Compliance Guidelines  ==
 
== Internal IP Compliance Guidelines  ==
 
+
We have a first draft [[Swordfish:ProjectRules:IPComplianceProcess_Internal|Internal IP Compliance Process]] to be discussed and reviewed by the team.
The Eclipse Legal Process guidelines provide all Swordfish team members with all the information required on the subject of IP compliance. Here are a few links on the Eclipse IP Legal Process
+
12:34, 27 July 2009 (UTC)
 
+
*[http://wiki.eclipse.org/IP_Stuff| This provides you with excellent background information].
+
*[http://www.eclipse.org/projects/dev_process/ip-process-in-cartoons.php| The Eclipse IP Compliance Process in cartoon format!]
+
 
+
There is also an audio presentation worth listening to you at: [[http://live.eclipse.org/node/713|Janet Campbell, Legal Counsel & Manager, IP]]
+
 
+
In addition to this, in our team we have a short process work flow that all team members can use as a frame of reference. [[Image:Ip compliance wk committers.png|IP Compliance Work flow in Swordfish]]<br>
+
 
+
NOTE: This is a draft process guideline. It will be subject to review and improvement throughout the project life-cycle.
+
  
 
== Release Checklist  ==
 
== Release Checklist  ==

Latest revision as of 08:34, 27 July 2009

Contents

[edit] Methodology

Swordfish is developed using the scrum method.

[edit] Common definition of "Done"

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

[edit] 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.

[edit] 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)

[edit] 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