So, maybe it's about time to realize that information about a new release will leak and do something about it? I don't know the reasons for having the distribution laying around the usual place before it's released but I'm sure there must be good ones since everybody seems willing to go through this pain over and over again.
If it's impossible to fix this by hiding the directory, password protecting it or something similar during "flux time" this fact should certainly be communicated by other means than through slashdot notes.
Or at least touch "AAA - - - NOT YET RELEASED - - - EXPECT CHANGES - - -".
And no, I didn't post the FTP URL to make anyone upset. I just wasn't aware of this way of releasing software and I'm sure I'm not the only one.
Slashdot Mirror
So, maybe it's about time to realize that information about a new
release will leak and do something about it? I don't know the reasons
for having the distribution laying around the usual place before it's
released but I'm sure there must be good ones since everybody seems
willing to go through this pain over and over again.
If it's impossible to fix this by hiding the directory, password
protecting it or something similar during "flux time" this fact should
certainly be communicated by other means than through slashdot notes.
Or at least touch "AAA - - - NOT YET RELEASED - - - EXPECT CHANGES - -
-".
And no, I didn't post the FTP URL to make anyone upset. I just wasn't
aware of this way of releasing software and I'm sure I'm not the only
one.
It's here, anyway:. 2-RELEASE/
ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/5