Future plans

Edit Releases

Status: Completed in version 0.6

I'd like to add the ability for SF users to be able to edit releases (as well as the current ability to create releases).

Integrate Announcements

Status: Completed in version 0.7

Allow ReleaseForge users the ability to create a news announcement of their new release within SourceForge.

Freshmeat Integration

Status: Completed in version 0.8.0

ReleaseForge Users can now release project announcements to Freshmeat.

Mailing List Integration

Status: Completed in version 0.9.0

Allow ReleaseForge users the ability to create an announcement to one or more mailing lists.

Google Groups Integration

Status: Requires user feedback and interest

Similar to the previous items, allow ReleaseForge users the ability to post their new release announcement into one (or more) usenet groups using Google Groups

Improved Freshmeat/SourceForge integration

Status: Planned

Currently, SF projects can be linked to Freshmeat projects. However, in the future, a SF project package can be linked to a Freshmeat project. So a SF project with several packages can have each of the packages linked to a seperate Freshmeat project.

Web Page Upload

Status: Not possible

A number of ReleaseForge users have contacted me in order to add a feature that would allow SourceForge users the ability to scp files from their local computer to SourceForge's web project server.

I would definitely add this feature if it were possible, however, in my research I have not found a reliable way of integrating scp functionality within a Python GUI environment that would be platform independent. Neither python nor Qt (QProcess class) is capable of capturing the interaction between scp's password prompt due to the nature of OpenSSH's implementation of password prompts.

If somebody knows of a way to reliably intercept the password prompt from scp within python or Qt that works equally well on Windows and Linux please feel free to contact me.

In theory though, a user could scp files to SourceForge using key authentication (rather than passwords) so basic functionality could be added. However, most users do not use key based authentication with SourceForge.

Proxy Support

Status: Not likely

I created a prototype of allowing SF users the ability to use a proxy server (rather than a direct internet connection) however I ran into some complications:

  1. Python does not have the capability within the urllib2 module that supports https proxies. To my knowledge, urllib2 can only communicate with http proxies rather than their secure counterparts. SourceForge requires https for project admins.
  2. Python's ftplib does not support proxies. ReleaseForge uses a subclass of ftplib's FTP class to upload files to SourceForge's ftp server.

In theory I could use pycURL in order to contact SourceForge's site via an https proxy that would satisfy issue #1 above. However, this would introduce extra dependencies (cURL, pycURL, libcrypto, kerberos, libssl, etc...) that might be too difficult for the end-user to use. I would much rather use python's modules (urllib2) to implement proxy support over https since that is currently how ReleaseForge interacts with SourceForge directly rather than use 3rd party package(s) which would also require me to rewrite a significant portion of code.