web download links

[Bob Carpenter]

Daniel and I were discussing how to organize the web pages.
With a beta release for 2 coming up and older versions, I
think we need a layer of indirection.

Something like a home page and then a per-product download page.
It's going to get too big with Python and then with MATLAB and maybe
even Stata. And all the versioning is too busy for the home page.

So I'd suggest something like this, which I'd be happy to code up
today before the 2.0 release-candidate goes out.

- Bob

HOME PAGE
=====================
...

MANUALS
-----------------
- Programming Guide
- Reference Manual
- Example Models

DOWNLOAD STAN
-----------------------------------
- RStan Download Page
- Command-Line Stan Download Page
- PyStan Download Page



RStan DOWNLOAD
=========================

Includes Stan source code.

Licenses
--------
RStan: GPLv3
Stan: new BSD


RStan 1.3.0 (Latest Stable Release)
--------------------------------------
...

RStan 2.0.0-1 (Latest Development Release)
-------------------------------------------
...


GitHub Source Repository
------------------------------------------
....

Older Releases
-------------------------------------------
...

[Jiqiang Guo]

rstan is not provided by downloading its source (though it can be if a user knows how to install from a packaged source).  So in general, only one version of rstan can be pointed to automatically using current installation method. 

--

Jiqiang 

--
You received this message because you are subscribed to the Google Groups "stan development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stan-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Bob Carpenter]

On 10/14/13 7:09 PM, Jiqiang Guo wrote:
> rstan is not provided by downloading its source (though it can be if a user knows how to install from a packaged
> source).

Good point. I should just point from the Stan home
page to your install instructions.

The Stan command-line page will then look like what
I wrote.

> So in general, only one version of rstan can be pointed to automatically using current installation method.

Why can't we just select a different URL for 1.3.0 and
2.0.0-1?

Do the instructions for using it change much? I just
wonder because there's also the getting started Wiki.

- Bob

[Jiqiang Guo]

We can set up another set of repository for rstan candidate release.  The drawback is that 

* it would be empty if we do not have candidate release

* if users set up the repo for the candidate release, they could not install the stable release as the version of bigger number would be picked up by R automatically.  To install the stable release, one way is to restart R. 

In addition, if we ask users to use library devtools to install R, we can ask users do something like the following webpage shows. If we use this way, we do not need to depend on the google code stuff any more. 

https://github.com/stan-dev/rstan/releases

--

Jiqiang

- Bob

[Bob Carpenter]

On 10/15/13 6:10 PM, Jiqiang Guo wrote:
> We can set up another set of repository for rstan candidate release. The drawback is that
> * it would be empty if we do not have candidate release

In the future, we plan to stage things so we release Stan
first, and then RStan, Command-line Stan, and PyStan would all
work from that.

For now, we've tied in command-line Stan to Stan itself, but
RStan is decoupled in the sense that we only point to the install
instructions.

> * if users set up the repo for the candidate release, they could not install the stable release as the version of bigger
> number would be picked up by R automatically. To install the stable release, one way is to restart R.

If we have multiple releases up on your releases page,
then can you add some instructions for how users can
change either going forward or backward (that is, how
to start/stop/install in R). Thanks.

> In addition, if we ask users to use library devtools to install R, we can ask users do something like the following
> webpage shows. If we use this way, we do not need to depend on the google code stuff any more.
>
> https://github.com/stan-dev/rstan/releases

This is great news. Should've read it before sending
out the last message. I'll delete Google Code.

- Bob

[Marcus Brubaker]

Just a thought, would it be easier if release candidates were something like 1.99.0 instead of 2.0-RC?  It sounds like this might simplify things on the RStan side and doesn't cost us anything otherwise.

Cheers,

Marcus

- Bob