RL2 Release plan: we need you!

[Stray]

Robotlegs 2 is coming!

There are just a few housekeepingy-things we need to sort out, and then the intention is:

RC1: Current API to go out into the wild for testing

RC2: Performance focussed release with API matching RC1 (aka The Linkedlistification)

RC3+: Bug fixes and API tweaks as needed

We'd love to have a list of those who are interested in feeding back on the API and, separately, a list of folk who would like to be involved in the code review for RC2, with an eye on improving performance.

Please declare below if you'd like to be involved in API review, performance review (or both) and/or building examples. State which you'd want to be involved in and the best method for contacting you so we can give you a heads up when there are things to look at, and I'll try to keep my lists below in line with your wishes.

Thanks!

Stray

---

API Review:

@troygilbert @alecmce @creynders @hyzhak @quentint @GV3

Performance review:

@troygilbert @alecmce @tdavies @wrobel221 @GV3

Examples:

@peterkeating @quentint @zedia

[troygilbert]

I don't have time to write any examples (at least, not any good ones), but would love to give it an once (or twice) over with an eye towards performance. I'm also sure I couldn't help myself when it comes to comments on the API either. ;-)

[alecmce]

Are there any performance tests available? I'm guessing we'll need to make them but want to check in case there's already a baseline we can use.

[darscan]

Not yet - I hacked together a simple performance test harness thing recently (I tried to use GSkinner's one, but it kept exploding). I'll stick it in a repo in case it's useful.

[darscan]

Here's that dirty thing: https://github.com/darscan/robotlegs-performance-harness

[darscan]

The version2 branch has been merged into master!

[Stray]

Hurrah!

[rhysturner]

Fantastic news guys! Great job!

[peterkeating]

Great to hear that RL2 is on the horizon! Happy to hear any ideas you guys have for examples that will be of use. Really glad to be able to help out :)

[creynders]

API review, with pleasure!

[tdavies]

Great work guys. I'll give it a look over with performance in mind and let you know my thoughts.

[Stray]

@creynders added!

@tdavies We've currently left it so that it's completely unoptimised and written for clarity, so there will be much to do.

[quentint]

Can do API review and could contribute some examples (currently working on a pretty large RL2 app from which I could extract use-cases…) Ping me via Github or Twitter!

[hyzhak]

yes! i been waiting for this release for a long time. I will look through API with pleasure.

[Stray]

Hey all, @darscan will be taking over running the lists / timing for reviews. So - any questions, give him a poke. Still add names/offers here.

[zedia]

I would be interested in doing examples, I guess I would have to learn it first. I am pretty used to RobotLegs 1, but not sure just how much changed.

[vrobel]

OK. I'll also be available for performance review.

[darscan]

@zedia That's actually great, because we also want to capture thoughts on first-time usage/migration: https://github.com/robotlegs/robotlegs-framework/issues/101

[GV3]

In for both reviews, especial interest in the performance.

[darscan]

I've uploaded a snapshot of version 2.0.0b1 to the download area.

[darscan]

GitHub has deprecated the downloads area. This link will be active for a little while still:

https://github.com/robotlegs/robotlegs-framework/downloads

[darscan]

Beta 3 is up. Due to the deprecation of GitHub Downloads, the latest build can be found on the RL website: http://www.robotlegs.org/

[darscan]

Beta 4 is up. This release fixes some timing issues with the Modularity extension and introduces a new extension called StageCrawler.

[darscan]

So, I think RL2 is basically ready for release. I'm pretty happy with it.

However, whenever anyone actually uses it (and provides concrete feedback) I seem to find things that can be fixed/improved. But that could keep going on forever, so..

Perhaps we should just pick a date? Like Friday the 8th of February? A deadline; two weeks to dig in and make sure the API is sound. How about it?

[tschneidereit]

Sounds like a plan!

I'd even go as far as releasing Swiftsuspenders 2.0 in time for that. :)

[darscan]

Ah! That reminds me... We need to consolidate Stray's Swiftsuspenders fixes (I don't have a grasp on them unfortunately). RL2 is still being built against her fork.

[tschneidereit]

Indeed we do! I'll have time for that next week, let's talk then, ok?

[alecmce]

I haven't had a chance to look at performance. I'm afraid I'm largely in Haxe these days.

[darscan]

@tschneidereit Ok, great! @alecmce No problemo. We can look at performance for the next minor release. For now we just have to make sure the API is sane.

[darscan]

Some fairly tricky issues have been reported this week. I'm going to postpone the release until Sunday to give me some time over the weekend to tackle them.

[darscan]

Nope, there's just too much to do, and not enough time right now. I have to push this out a bit further. Apologies.

[pixels4nickels]

I will write examples if someone wants to give me a few topics. I been breaking into my new job at Kixeye but finally starting to have spare time again. Been pushing for some refactoring here at the company, specifically using Ash and RL2

[darscan]

Thanks Ken! I find it really hard to come up with simple demo apps. Any ideas you might have would be great

[pixels4nickels]

I am going to take some of the more common RL1 demos and start rewriting them. It will serve as my kata for a bit.

[darscan]

This thread isn't providing much value, so I'm closing it for now.