bypassing beta or rc release

[Bob Carpenter]

Daniel and I don't have the patience to sort out a beta
release and then a regular release --- it's too much fiddling
with tags, versions in R and Python, and too many changes
to the web page.

We should release Stan 2.0 in the next day or two. We're
almost there.

- Bob

[Ben Goodrich]

I wouldn't object to releasing 2.0 without doing a prerelease, but how can Stan 2.0 be almost there if there isn't even a release-2.0 branch from development yet?

[Daniel Lee]

Ben, you're right -- we messed up the process by not having a release/v2.0.0 branch. We've already started some of the process on the develop branch when we shouldn't have.

I'll create that branch after the fixes to the manual. I'll use that branch to add the built manual and doxygen to the repository.

I'll try to be more careful next time.

Daniel

--
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]

"almost" is a relative term :-) We're about ready to
check in the last bits of the manual. The code's frozen.

- Bob

[Ben Goodrich]

The development branch is never supposed to be frozen under gitflow, although maybe we don't have enough manpower to always be merging pull requests. There is supposed to be a release branch from development that is not totally frozen either but only has release-related commits like bumping version numbers and stuff.

Ben

[Bob Carpenter]

On 10/15/13 8:28 PM, Ben Goodrich wrote:
> The development branch is never supposed to be frozen under gitflow, although maybe we don't have enough manpower to
> always be merging pull requests. There is supposed to be a release branch from development that is not totally frozen
> either but only has release-related commits like bumping version numbers and stuff.

Thanks for the reminder --- we're not very well trained
yet!

As soon as you mentioned a release branch, it rang a bell for
Daniel and he started one. It's sort of a cargo-cult release
branch because develop had already been treated like a release
branch. But it'll be good practice for next time.

- Bob