33.0.0-pre3

[bjarteskogoy]

Just wondering how far away this release is. Will this be cef 1750 and having the jsbinding work merged?

[amaitland]

33.0.0-pre3 will indeed be based on 1750, I believe it'll just be what's in master as it stands so no JS Binding.

I'm hopeful that we'll get CI setup in such a way that we'll have dev nuget packages published to myget shortly, and we'll include JS Binding packages there.

The JsBinding_WIP branch is awaiting peer review, so just have to wait for one of the other guys to find time.

[amaitland]

As for how far away, hopefully very soon! It's been way too long between releases.

[jornh]

33.0.0-pre3 will indeed be based on 1750, I believe it'll just be what's in master as it stands so no JS Binding.

Agree! On a related note I think we should take off the -pre label on cef.sdk and cef.redist, they're built on an official CEF release. @amaitland care to do that and push to staging?

I'm hopeful that we'll get CI setup in such a way that we'll have dev nuget packages published to myget shortly, and we'll include JS Binding packages there.

Another, controversial? 😛 option I thought about would be to simply release master + #492 as 33.0.0, without the -pre then we would just need to stick a fat warning sign on that if you need JsBinding either stay on CefSharp1, or preferably go with the future: #310 released as our new -pre ASAP right on the heels of the other one.

This would serve two purposes:

• Encourage switchover from CefSharp1, I guess many NuGet users simply choose stable because it's the default. And we really don't have the time to support CefSharp1.
• Expose JsBinding even more sooner as our new -pre to those who need it, right there on the official NuGet feed.

Thoughts?

[amaitland]

Agree! On a related note I think we should take off the -pre label on cef.sdk and cef.redist, they're built on an official CEF release. @amaitland care to do that and push to staging?

Sure, happy to. Prob be tomorrow at this rate 😄

Another, controversial? 😛 option I thought about would be to simply release master + #492 as 33.0.0, without the -pre

Very interesting idea indeed! I like it 😄 Added bonus of reducing the number of CefSharp1 support queries.

I hadn't even considered releasing #310 as a -pre release, makes a lot of sense. I think the API is fairly stably, so any changes are more than likely to be in the internals. I believe a number of people are using it already with success. Subsequently it would be fantastic to answer peoples queries about JSBinding with a simple, try our nuget -pre release so 👍 from me to the whole idea!

I'm thinking we go for 33.0.0 as you suggested, and release JSBinding as 33.1.0-pre01. That gives us the option to release 33.0.1 etc as bugfix releases. Thoughts?

[bjarteskogoy]

Sounds very good!

[Healian]

after hearing this i think i will wait and not use cefglue... cefsharp is amazing i like the way it is coded.

[Healian]

@amaitland is there any estimation of when 33.0.0-pre3 will come out. i mean do i wait for it. @jornh

[amaitland]

Unsure, hopefully soon. Really depends when everyone has spare time, so it's a little hard to say.

[jornh]

I've updated https://github.com/cefsharp/CefSharp/milestones numbers and descriptions to reflect my understanding of what we discussed so far. Thoughts?

What's the next steps?

[amaitland]

@jornh You have been busy, very nice! The descriptions look spot on 👍

I guess we start building packages? Possibly build a whole set, push them to staging, leave them sit there for a week, let the dust settle, if things go well we push to nuget proper?