I'll fix the access rights.

On Tue, Mar 4, 2014 at 9:26 AM, Damien Regad <dregad@mantisbt.org> wrote:
On 2014-03-04 16:19, Victor Boctor wrote:
> I've updated the blog to point directly to the MantisBT downloads page.


>   We can also change the downloads page to point directly to sourceforge
> 1.2.17 folder.  I think it is a good idea for all downloads to flow
> through the site download page rather than directly to sourceforge.
>   This will make it easy for us to move to other downloads options
> (e..g. host the release files on our server or a service like S3 /
> CloudFront)..

I am not really sure why we would want to do that, what would be the
benefits of switching services ? I think sourceforge is quite good for
our purposes. Anyway, if you want to keep it transiting through
mantisbt.org at the expense more clicks for users, fine by me.

> Once we reference the 1.2.17 folder directly, we should make sure to
> update the website only once sourceforge is updated.

Not really a blocking point actually, Sourceforge just redirects invalid
URLs with a popup message mentioning the file was not found e.g. :

        goes to

But you're right, it would be best to do things in sequence (sf upload
then mantisbt.org update) - which just means more work for you - unless
you grant me release technician rights. Your call.


Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
mantisbt-dev mailing list