#1034: bouncycastle and bouncycastle-mail should be in a chain

[Fedora Release Engineering]

#1034: bouncycastle and bouncycastle-mail should be in a chain
------------------+---------------------------------------------------------
 Reporter:  oget  |       Owner:  rel-eng at lists.fedoraproject.org
     Type:  task  |      Status:  new                            
Milestone:        |   Component:  cvs                            
 Keywords:        |  
------------------+---------------------------------------------------------
 Hi, I am the maintainer of bouncycastle-mail (bcmail) and comaintainer of
 bouncycastle (bcprov).
 Today, I requested an F-9 branch for bcmail. Once it is done I will update
 bcprov to the latest version and also I will build bcmail for F-9.

 The thing is, bcmail directly depends on bcprov, version-wise. So bcprov
 can't be updated without updating bcmail and vice versa. Actually this is
 true for all the branches (F-9, F-10, rawhide).

 I am not sure what the exact procedure is (I couldn't find it in the
 guidelines) but someone suggested me to contact you. So I have two
 questions:

 - How can I make a chain build of both bcprov and bcmail for F-9?
 - If, at a later time, I need to update all the branches to a newer
 version how will the tagging of both bcprov and bcmail go?

 Thanks.

 Ref: bcmail cvs request:
 https://bugzilla.redhat.com/show_bug.cgi?id=465382

-- 
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/1034>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project