[Blends-commit] [SCM] blends-dev branch, master, updated. 4f15e66d6876d25900861aad33b0d8cb089f350a

[Andreas Tille]

The following commit has been merged in the master branch:
commit 931cf97d4e9c8d980859e6e82b4dcd4faf180e63
Author: Andreas Tille <tille at debian.org>
Date:   Sun Feb 2 00:42:56 2014 +0100

    Add new QA for FAW: DebTags

diff --git a/doc/en/D_faq.xml b/doc/en/D_faq.xml
index e26bb5a..66f90db 100644
--- a/doc/en/D_faq.xml
+++ b/doc/en/D_faq.xml
@@ -145,5 +145,57 @@ interesting packages for their work.  This is a waste of time since:
 </para>
    </sect1>
 
+   <sect1 id="DebTags">
+   <title>Why not simply using DebTags?</title>
+<para>
+In general I'd like to quote Enrico Zini about the relation of DebTags
+and Blends tasks:  "Both efforts are orthogonal to each other and a well
+designed task should cover a specific workfield which is not necessarily
+given due to the fact that a package belongs to a certain (DebTag)
+category."
+</para><para>
+Moreover if you exclusively rely on the DebTags you are ignoring additional
+options the Blends framework is providing.  For instance the 
+<ulink url="http://blends.debian.org/med/tasks/bio">Biology task of Debian Med</ulink>
+contains several sections about packages which are not yet available in the
+Debian package pool.  This includes:
+<orderedlist>
+  <listitem><para>
+    Packages inside the new queue
+  </para></listitem>
+  <listitem><para>
+    Packages the team is working on in VCS
+  </para></listitem>
+  <listitem><para>
+    Inofficial packages at some other places
+  </para></listitem>
+  <listitem><para>
+    Information about not yet packaged software that might be of certain interest
+  </para></listitem>
+</orderedlist>
+This turns out as a very useful todo list to grab work items from as well
+as information to prevent duplication of work.  (Yes ITP bugs do not always
+work out that reliably.)
+</para><para>
+The Blends framework works quite nicely automatically if packages "upgrade"
+from one section to the other which means if you specify a package which has
+only some packaging in VCS it is sufficient to simply add a dependency to
+the tasks file and it shows up
+<ulink url="http://blends.debian.org/med/tasks/bio#pkgvcs-debs">here</ulink>
+(to stick to our example above).  So all relevant information is just taken
+from VCS and if you for instance change the description in your packaging
+the tasks page will be updated automatically (after some cron job delay).
+</para>
+<para>
+Once the package might be uploaded the first time it migrates to the
+section named "Debian packages in New queue (hopefully available soon)"
+(which is only available if there are such packages) and finaly once
+ftpmaster might have accepted the package it shows up in the tasks ...
+even not yet DebTagged.  You have another delay until the DebTag information
+is propagated properly and thus relying on DebTags in this whole proces
+does not work.
+</para>
+   </sect1>
+
   </appendix>
 

-- 
Git repository for blends code