Author: patrys Date: Mon Oct 1 10:15:55 2007 GMT
Module: PLDWWW URL:
http://pld-linux.org/DevelopingPLD?action=diff&rev2=34&rev1=33
---- Log message:
---- Page affected: DevelopingPLD
---- Diffs:
================================================================
Even if there is only one message in your commitlog, prefixing it with a dash
will make reading it a lot easier.
+ === Package's life cycle ===
+
+ 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. 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.
+ 1. The package is moved to the queue tree ({{{ready}}} for Ac and {{{test}}}
for Th).
+ 1. Your RM takes further care of the package. He decides when the package is
ready to be moved to the stable tree (or the {{{updates}}} tree in case of an
already released version). If you believe it takes too long, check if all the
dependencies (both introduced or broken by the particular package) have been
satisfied in the queue tree.
+ 1. The package is finally moved to the stable or {{{updates}}} tree and
anyone can use it.
+
=== Resolving common problems ===
- [:DevelopingPLD/AdvancedDeveloping/FixingAsNeeded: Fixing --as-needed
problems]
_______________________________________________
pld-cvs-commit mailing list
[email protected]
http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit
