PLDWWW: DevelopingPLD

[gotar]

Author: gotar   Date: Sat Jun 20 14:40:05 2009 GMT
Module: PLDWWW   URL: http://pld-linux.org/DevelopingPLD?action=diff&rev2=39&rev1=38
---- Log message:
fixed CVSweb links

---- Page affected: DevelopingPLD

---- Diffs:

================================================================
The comment on the change is:
fixed CVSweb links

  Before you decide you are done, double-check your dependencies section for all necessary packages and make sure the package builds cleanly (for instance, no files are left after packaging RPM files - {{{builder}}} warns about that at the end of building process).
  
  If you're bored and don't know what to do, you can try fulfilling requests from
- [http://cvs.pld-linux.org/PLD-doc/PLD-specs-TODO?rev=HEAD PLD-doc/PLD-specs-TODO](or this same list but with additional entries on wiki [http://pld-users.org/specs-todo]),
+ [http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/PLD-doc/PLD-specs-TODO?rev=HEAD PLD-doc/PLD-specs-TODO](or this same list but with additional entries on wiki [http://pld-users.org/specs-todo]),
  or autogenerated TODO headers from *.spec:
- [http://cvs.pld-linux.org/PLD-doc/specs-auto-todo.txt?rev=HEAD PLD-doc/specs-auto-todo.txt]
+ [http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/PLD-doc/specs-auto-todo.txt?rev=HEAD PLD-doc/specs-auto-todo.txt]
  
  === Publishing your changes ===
  
@@ -114, +114 @@

  After a {{{spec}}} file gets commited, the package needs to be built. The life cycle is as follows:
  
   1. {{{spec}}} file is commited (including changes to needed patches and other files referenced in the {{{spec}}})
-  1. One of the developers requests a test build (this is done using the [http://cvs.pld-linux.org/pld-builder.new/client/make-request.sh?rev=HEAD make-request.sh] script). If you don't have the rights contact your RM for access. It is possible to skip this step and ask for an upgrade directly however it is not recommended as a partial upgrade results in desynchronising packages between build servers. If found guilty, you will be executed on the spot.
+  1. One of the developers requests a test build (this is done using the [http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/pld-builder.new/client/make-request.sh?rev=HEAD make-request.sh] script). If you don't have the rights contact your RM for access. It is possible to skip this step and ask for an upgrade directly however it is not recommended as a partial upgrade results in desynchronising packages between build servers. If found guilty, you will be executed on the spot.
   1. The package is successfully built on all architectures.
   1. One of the priviledged developers requests an upgrade build (same script as above) - contact your RM for access.
   1. The package is once again built on all architectures and upgraded across the whole builder farm.