Mavericks

[Patrick Robertson]

With Mavericks set for GM, and our v1.1.1 update looking a long way off, I think we should:

* Make a 10.9/bugfixes branch.
* Merge anything relevant from master to this branch (I can only think of the blue selector round elements bug)
* Release v1.1.1 ASAP
* Strangle ourselves over the objectDictionary a little longer ;-)

[Rob McBroom]

In theory, we could make a branch off of the latest tag. I haven’t tried it in practice, but I’ll check into it.

I’ll look through merged changes for any major bugs, but of the top of my head, all we really need are:

* The selection ring fix
* The OS version detection thing. (I’d like to be able to get the tagging plug-in out on release day or sooner. It’s ready.)

I’ll do a fix to the OS version pull request to check min and max.

--
Rob McBroom
<http://www.skurfer.com/>

[Patrick Robertson]

Yeah it's pretty easy:

git checkout -b mavericks v1.1.0

Agreed on what you're saying. I'll make File Tagging a priority (although I don't have my HDD and therefore VM with me this weekend)

On IRC if needs be

> --
> You received this message because you are subscribed to the Google Groups "Quicksilver - Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to quicksilver---deve...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

[Rob McBroom]

On Fri Oct 04 2013 at 08:32:31, Patrick Robertson wrote:

> Yeah it's pretty easy:
>
> git checkout -b mavericks v1.1.0

Here’s the branch so far.

https://github.com/quicksilver/Quicksilver/compare/v1.1.0...release?expand=1

I’ll cherry-pick the two commits from #1629 as well, if you think it looks OK.

After that, I’ll just put a final release straight out, since the changes are so small.

[Guy Manchester]

Still no fix for Clipboard under Mavericks?

[Rob McBroom]

On Fri Oct 04 2013 at 15:55:48, Guy Manchester wrote:

> Still no fix for Clipboard under Mavericks?

None of us had time to look into it until today. I wasn’t able to reproduce it (history was captured fine), so… no. Sorry.

Didn’t you report it on GitHub? I thought you had, but wasn’t able to find the issue this morning when I was investigating.

[Guy Manchester]

No, I didn’t get round to opening an issue on Github - my bad, apologies!

I did start a thread about it on here (HERE) and Patrick said:

I'd forgotten that I hadn't finished downloading Xcode yet, so can't debug right away (don't worry, I'm only 200MB and 6 hours away from completion…

So I probably should have chased that up 6+ hours later - my bad again! 

I’ve now opened an issue on Github anyway.

-- 
Guy Manchester
Sent with Airmail

[Rob McBroom]

On Sat Oct 05 2013 at 05:57:54, Guy Manchester wrote:

No, I didn’t get round to opening an issue on Github - my bad, apologies!

I did start a thread about it on here (HERE) and Patrick said:

I'd forgotten that I hadn't finished downloading Xcode yet, so can't debug right away (don't worry, I'm only 200MB and 6 hours away from completion…

So I probably should have chased that up 6+ hours later - my bad again! 

I’ve now opened an issue on Github anyway.

Not saying you had to. I just thought it might have some additional detail. I didn’t do a clean install, so that’s something I can look at when setting up a new 10.9 VM.

FYI, I pushed a couple of post v1.1.2 changes straight to master. The changes in 1.1.2 were already part of master (as you know) but were cherry-picked over to it, so that branch will live on its own and never be merged. I just pulled its release notes over and bumped the build number.