Thanks! I will try the dry run idea, and thanks for the tip on sf. I
think I got an email about that but it wasn't immediately clear to me
that it applied . . . .
Adam
On Jun 9, 2009, at 4:43 PM, Christiaan Hofman wrote:
> If you're not completely confident you could do a dry run of the
> Di
If you're not completely confident you could do a dry run of the
DiskImage build steps, so you can test it out before committing the
last changes. As for the changes to the procedure, the main difference
for you is updating the appcast (bibdesk.xml), but that's not too
critical because that
On Jun 9, 2009, at 3:20 PM, Maxwell, Adam R wrote:
> Sorry, I didn't know the procedure had changed...that's a real pain,
> especially if you're not responsible for the changes, so have to
> figure out
> the process all over again! The only time I was comfortable with
> releases
> was when I'
Sorry, I didn't know the procedure had changed...that's a real pain,
especially if you're not responsible for the changes, so have to figure out
the process all over again! The only time I was comfortable with releases
was when I'd been doing them once a month for an extended time, since there
are
Yes there is, and every day I say, I will do it today . . . OK, now I
really, really will. It is a new procedure this time so I am a little
nervous about it.
Sorry for being such a lame release technician. I do think I will be
better at getting things out sooner as I have been more on and mo
Is there any chance of getting a release out soon? A colleague asked today
why Google Scholar support was broken. I pointed him to the nightly
builds...but it would be nice to have an "official" version out there, since
that feature has been broken for ~4 months.
---
