tags or point releases for major changes in stan (was: merging arg_refactor into develop)

[Allen Riddell]

Hi all,

Is there any interest in having a few reference points to the stan develop
source, e.g., some way of referring to pre arg_refactor and post arg_refactor?
A point release would work (e.g., 1.3.1, alpha, beta, etc) or even a git tag
with a date.

I ask because right now it's difficult to know what changes require
modifications to the PyStan wrappers without digging deep into the rstan
commits.

Thanks,

Allen


On 08/21, Bob Carpenter wrote:
> The arg_refactor branch is messing up other pull requests
> which are being done relative to develop, and will then need
> to be redone for consistency with arg_refactor. This includes
> the RStan and PyStan interfaces, Marcus's work on optimization,
> etc.
>
> I'd like to get a stable (i.e., passing all unit tests) version
> merged ASAP. It doesn't need to be complete --- we can continue
> to make pull requests after the merge.
>
> Is there anything broken that is stopping us from merging now?
>
> - Bob
>
> --
> 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+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

[Bob Carpenter]

Exactly why we're trying to merge arg_refactor ASAP.
Then you could just continue to work vs. the develop branch.
We don't plan to continue to support 2.0.

On the other hand, the arg_refactor is mainly for the command
line, so shouldn't have a big impact on PyStan or RStan. The
refactoring of the MCMC is already merged into develop.

We do hope to get 2.0 out soon. I think we've dealt with
all of the major bugs and just need to make sure the new
command-line is robust and documented.

- Bob