Bug 763991 (GLUSTER-2259) - Please improve the FTP structure
Summary: Please improve the FTP structure
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-2259
Product: GlusterFS
Classification: Community
Component: unclassified
Version: mainline
Hardware: All
OS: All
low
low
Target Milestone: ---
Assignee: Vijay Bellur
QA Contact:
URL: http://download.gluster.com/pub/glust...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-30 17:10 UTC by Patrick Matthäi
Modified: 2015-12-01 16:45 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: All
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Patrick Matthäi 2010-12-30 17:10:33 UTC
Hello,

please also add a symlink on your FTP, which points to the most recent version.

Currently there is the following structure on http://download.gluster.com/pub/gluster/glusterfs/ =>

- VERLINE_2.x
- VERLINE_3.0
- VERLINE_3.1
- Some other foo

In every VERLINE folder is a link (LATEST) which points to the most recent version of this version line.
So please also add on /pub/gluster/glusterfs/ another link (LATEST?) which points to the most recent version.

This improves the monitoring of new releases @ Debian.

Comment 1 Vijay Bellur 2011-01-15 07:30:46 UTC
LATEST added to http://download.gluster.com/pub/gluster/glusterfs

Comment 2 Patrick Matthäi 2011-04-19 15:30:45 UTC
Hi,

the link http://ftp.gluster.com/pub/gluster/glusterfs/LATEST/ has been gone again :(

Comment 3 Lakshmipathi G 2011-04-20 04:37:26 UTC
(In reply to comment #2)
> Hi,
> 
> the link http://ftp.gluster.com/pub/gluster/glusterfs/LATEST/ has been gone
> again :(

Sorry,Its fixed now. :D

Comment 4 Shwetha H Panduranga 2011-09-20 01:39:10 UTC
http://download.gluster.com/pub/gluster/glusterfs/

The top Level folder i.e. pub/gluster/glusterfs/ has the link LATEST.

Even though 3.1.7 is the latest glusterfs release LATEST is pointing to 3.2.3 glusterfs release since 3.1.x is going to be end of life. (As per discussion with Vijay)


Note You need to log in before you can comment on or make changes to this bug.