You can upload custom files as releases, and you can even do it from CI systems like Travis. Yet, I think releases should stay at fdo (although the CI could generate that one, too). <div class="gmail_quote"><div dir="ltr">On Sun, Oct 30, 2016, 23:31 George Kiagiadakis <<a href="mailto:gkiagia@tolabaki.gr">gkiagia@tolabaki.gr</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 10/31/2016 12:15 AM, Alexandr Akulich wrote: > Hi George, > > thank you for the summarize. I have no time for a verbose answer, but > would like to make some note. > > We can not use "Github releases" feature, because: > 1) We need to prepare release in some special way. Namely, we generate > documentation for release tarballs. Github archives contains only the > tree snapshot from a tagged commit. > 2) The archive directory name is project name + tag name. For > TelepathyQt we have archive "telepathy-qt-0.9.7.tar.gz" with directory > "telepathy-qt-telepathy-qt-0.9.7". > > I think we should use <a href="https://telepathy.freedesktop.org/releases/" rel="noreferrer" class="gmail_msg" target="_blank">https://telepathy.freedesktop.org/releases/</a> , but > I didn't checked yet if we can place sources of new components > (TpQt-based CMs) there (probably we can do it without help from admins). > Yes, releases should and will happen like before. There is no need for admin access, we all have write permissions there. _______________________________________________ telepathy mailing list <a href="mailto:telepathy@lists.freedesktop.org" class="gmail_msg" target="_blank">telepathy@lists.freedesktop.org</a> <a href="https://lists.freedesktop.org/mailman/listinfo/telepathy" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.freedesktop.org/mailman/listinfo/telepathy</a> </blockquote></div>