timing myself out on release today

[Bob Carpenter]

I'm afraid I timed out for the release because now
I have to go to another meeting which I'm already
ltae for.

Other than printing int expressions in the division
operator grammar, everything I want is checked in.

I did put the new manual up on our site.

If the release is going to go out today, someone
else will have to do it. Otherwise, I can take this
up again tomorrow.

- Bob

[Daniel Lee]

I vote for a tomorrow release. I need to set up the profile on the
windows machine so Jenkins can push our website for us.

> --
>
>

[Bob Carpenter]

On 10/24/12 4:03 PM, Daniel Lee wrote:
> I vote for a tomorrow release. I need to set up the profile on the
> windows machine so Jenkins can push our website for us.

Yeah, we're having a real pile up on git pushes
right now, so I'm assuming not everyone else is
ready to go, either. I can regenerate the manual
with a new date and reload it if that changes between
now and when we release.

In fact, I'm going to go remove it now so nobody
gets confused.

For instance, are we going to do anything with the
diffs version of the manual Ben's been working on?
Are we going to put two copies up or what?

- Bob

[Daniel Lee]

On Wed, Oct 24, 2012 at 4:08 PM, Bob Carpenter <ca...@alias-i.com> wrote:
> On 10/24/12 4:03 PM, Daniel Lee wrote:
>>
>> I vote for a tomorrow release. I need to set up the profile on the
>> windows machine so Jenkins can push our website for us.
>
>
> Yeah, we're having a real pile up on git pushes
> right now, so I'm assuming not everyone else is
> ready to go, either. I can regenerate the manual
> with a new date and reload it if that changes between
> now and when we release.
>
> In fact, I'm going to go remove it now so nobody
> gets confused.

Thanks. That sounds good for now.

> For instance, are we going to do anything with the
> diffs version of the manual Ben's been working on?
> Are we going to put two copies up or what?

I would want to put up two versions. One version of the manual should
always be a stand-alone manual.

[Ben Goodrich]

On Wednesday, October 24, 2012 4:11:28 PM UTC-4, Daniel Lee wrote:

> For instance, are we going to do anything with the
> diffs version of the manual Ben's been working on?
> Are we going to put two copies up or what?

I would want to put up two versions. One version of the manual should
always be a stand-alone manual.

Two manuals is fine with me, although there shouldn't be any differences except the bars in the margin and the backpage. The only thing is that someone who has the Lucinda font has to compile the diff'ed version for me, which means they have to follow these steps.

cd src/docs/stan-reference
./diff.sh v1.0.2 v1.0.3
cd ../../..
git apply alltt_patch_that_Ben_will_send_you.patch # but do not commit it
make clean-all
make manual
git reset --hard HEAD
# upload compiled PDF to website

The diff.sh is already pushed. I am just waiting for the v1.0.3 tag so that I can recreate the alltt*.patch that is about 5 lines.

Ben

[Ben Goodrich]

On Wednesday, October 24, 2012 5:43:38 PM UTC-4, Ben Goodrich wrote:

Two manuals is fine with me, although there shouldn't be any differences except the bars in the margin and the backpage. The only thing is that someone who has the Lucinda font has to compile the diff'ed version for me, which means they have to follow these steps.

cd src/docs/stan-reference
./diff.sh v1.0.2 v1.0.3
cd ../../..
git apply alltt_patch_that_Ben_will_send_you.patch # but do not commit it
make clean-all
make manual
git reset --hard HEAD
# upload compiled PDF to website

The diff.sh is already pushed. I am just waiting for the v1.0.3 tag so that I can recreate the alltt*.patch that is about 5 lines.

alltt.patch attached.

Ben

[Ben Goodrich]

BUT MAKE SURE BEFOREHAND THAT YOU DON'T HAVE ANY UNCOMMITED CHANGES SITTING AROUND IN YOUR MASTER BRANCH. Otherwise, they will get lost when you do git reset --hard HEAD.

Ben