[SoaS] Policy for activities for downstream inclusion

[Simon Schampijer]

Hi,

what is the current status for activity releases in order to include 
them in distributions like Soas*? Do you guys need tarballs or did you 
switch over to construct the rpms from the .xo? For example the latest 
Paint rpm uses the .xo AFAIK (build even the binaries from the 
non-python sources in the bundle).

And is the email from ASLO enough for packagers to know about new 
releases? Any other notification that packagers need?

Regards,
    Simon

* Of course any other downstreams that package/include activities are 
happy to reply to this email too.