Dave:
The "Downloads" link in the "Quick Links" on the right side of the project
blog goes straight to the Java.net site, and other users might experience
similar confusion.
We should either add some links from the Java.net page to point users to the
right place for Roller 2.3-incubating (and future) releases, start our own
Downloads page on the wiki, or point the Downloads link to the current News
page.
I clarified the text on the wiki section to indicate that the Downloads link
is for the Roller support materials and older Roller versions distributed
from Java.net, but there is still a lot of room for similar confusion.
--a.
----- Original Message -----
From: "Adam Henson" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, June 16, 2006 3:48 AM
Subject: Re: Issue - creating a blog with 2.3
Ah ok, thanks for that. I'm a little confused as to why the download link
is on the news page though..??
I decided to implement roller a couple of months ago, and a few weeks ago
got the time to do it, - so went to the Roller website and clicked on ->
Downloads. 2.1.1 is the latest listed download so I went ahead and
installed that. To be honest I'm more than a little annoyed at this, as
all of the trouble I've had with Roller seems to have already been fixed
in a download thats not listed on the Main downloads section of the
website.
Please, correct me if I've missed something, - it wouldn't be the first
time..
That 2.3 download should be added to the downloads link on the front page
ASAP!
Adam
[EMAIL PROTECTED] wrote:
http://rollerweblogger.org/page/project/news
Eric
-----Message d'origine-----
De : Adam Henson [mailto:[EMAIL PROTECTED] Envoyé : jeudi 15 juin
2006 18:31
À : [email protected]
Objet : Re: Issue - creating a blog with 2.3
Ah, it appears I am running 2.1.1-incubating. Going onto the roller
website though, this is the latest download listed?
Anil Gangolli wrote:
The actual release of Roller 2.3 includes this fix. This was ROL-1148
and was fixed in the last round of release candidates. If you don't
have this fix, you are probably running a release candidate (RC) and not
the actual released code. Make sure you have the official release.
--a.
