anchor.diff:  === Uploading the SDK and onejar
   
   1. SFTP to `build.eclipse.org`. You will need to provide your eclipse username and password.
  -2. Go to remote directory `/home/data/httpd/download.eclipse.org/rdf4j`. 
  +2. Go to remote directory `/home/data/httpd/download.eclipse.org/rdf4j`.
   3. Upload the SDK and onejar archives to this directory (NB we currently only distribute the SDK zip file, not the tar.gz file)
   
   == Minor and Major releases
  
positive.code: 
  1. The project's https://www.eclipse.org/projects/handbook/#ip-iplog-generator[IP log] needs to be filed and approved by the Eclipse legal team;
  +
  The IP log can be automatically generated and submitted to the legal team. Obtaining approval may require several days, so it's good practice to submit this at least two weeks before the planned release date. 
  2. The project's https://projects.eclipse.org/projects/technology.rdf4j[review documentation], part of the application, needs to be in order. 
  
  Typical review documentation can be a simple reiteration of the most important new features, a link to the issue tracker/release notes and documentation, and a remark about compatibility (if applicable). Once the review documentation is up, a mail needs to be sent to technology-pmc@eclipse.org to ask for approval. Here's an example of such a message, which was to get approval for the RDF4J 2.2 release:
  
  ----
  Dear PMC members,
  
  Can I get your approval for RDF4J release 2.2, scheduled for February 2. 
  
  Release review info: https://projects.eclipse.org/projects/technology.rdf4j/reviews/2.2-release-review 
  
  Issue tracking the release: https://bugs.eclipse.org/bugs/show_bug.cgi?id=510577
  
  
negative.code: 
  === Building and uploading SDK and onejar
  
  The SDK and onejar archives are hosted on https://www.eclipse.org/downloads/ . The archives need to be built locally, and uploaded manually, via secure FTP.
  
  === Building the SDK and onejar
  
  