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).
On Sun, Oct 30, 2016, 23:31 George Kiagiadakis <[email protected]> wrote: > 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 https://telepathy.freedesktop.org/releases/ , 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 > [email protected] > https://lists.freedesktop.org/mailman/listinfo/telepathy >
_______________________________________________ telepathy mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/telepathy
