New QS release?

59 views
Skip to first unread message

Patrick Robertson

unread,
Nov 14, 2015, 8:40:13 PM11/14/15
to quicksilver---development
What with all of Etienne’s (awesome) changes, is it worth us getting another release out?
I think it’s easier for us to maintain and fix bugs/regressions if we make smaller releases more often.

This could potentially be QS 1.4 - is there anything else we want to put in it?

Patrick Robertson

unread,
Nov 14, 2015, 10:58:15 PM11/14/15
to quicksilver---development
...wait a minute. Rob's already made a release? :-)

One step ahead, good to see!

Rob McBroom

unread,
Nov 15, 2015, 10:39:43 AM11/15/15
to quicksilver---development
On 14 Nov 2015, at 22:57, Patrick Robertson wrote:

> ...wait a minute. Rob's already made a release? :-)
>
> One step ahead, good to see!

Yeah, I was going to reply to your last message with “I’m glad you
feel that way” as it was about two hours after I had done it. :-)

I would also like to come up with an easy (not necessarily automatic)
way to do regular “Developer Previews”. I wouldn’t say
“nightly”, as that’s misleading, but a new build whenever
something merges to master would be cool.

FYI, I’m also working on moving the “all versions” page to the new
host, at which point we can kill the `gh-pages` branch and, if possible,
remove those huge files from the history.

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

Rob McBroom

unread,
Nov 15, 2015, 1:46:40 PM11/15/15
to quicksilver---development
On 15 Nov 2015, at 10:39, Rob McBroom wrote:

> On 14 Nov 2015, at 22:57, Patrick Robertson wrote:
>
>> ...wait a minute. Rob's already made a release? :-)
>>
>> One step ahead, good to see!
>
> Yeah, I was going to reply to your last message with “I’m glad you
> feel that way” as it was about two hours after I had done it. :-)

I meant to say the main reason for the urgency was the easily
encountered crash in our default interface.

> FYI, I’m also working on moving the “all versions” page to the
> new host, at which point we can kill the `gh-pages` branch and, if
> possible, remove those huge files from the history.

It’s all moved to /archives on the main host now. What should we do
about that branch?
Reply all
Reply to author
Forward
0 new messages