Triaging and Reviews – Release 0.4

With the recent finish (or almost finish due to one last ticket – linting), I figured I should write a blog post about it… considering we’re supposed to blog about each release… anyway, I also figured I’d start to set an example for Dave’s new students (whom I told to take the class), who are new to the world of blogs.

I took on a number of tickets for peer review.  Tickets #: 1, 42, 60, 61, 171, 188, 205.  Luckily, most of the code worked and had tests… so making sure they worked and the code looked simple and easy to read wasn’t too hard a task.

Ticket #1
This ticket was the first one inducted into lighthouse and it still hasn’t made the repo.  It was my job to make sure it passed.  It wasn’t very hard considering all of Daniel’s code looked great.  He did have an old test that wasn’t working anymore up.  I remember it working before though so I just took his code and plopped it into a newer instance and it worked.  I passed it for super-review.

Ticket #42
It was to fix the infinite loop happening in nf().  The fix looked simple enough that it didn’t even need to be tested.  I passed it for super-review.

Ticket #60, 61, 62
Andor’s release and awesome demo(needs 3D capable browser, like Minefield) proved it’s worth.  I, admittedly, didn’t even see the need to use the examples for a test.  I passed it for super-review.

Ticket #171, 188
The code was pretty straightforward using localStorage in the DOM.  I was a bit concerned about the tests slowing down my computer (as I could hear it struggling).  I brought this up to Corban and he said it was fine.  It was due to the strings being saved every time the canvas is redrawn (which was a lot).  I passed it for super-review.

Ticket #205
This was already pre-tested by me.  I used the tests that I wrote and plugged in sephr’s code.  It works well and is more efficient so I backed it and passed it for super-review.

Next release…

With 0.4 set, I am looking out for the next release.  Unfortunately, the code I checked in for 0.3 and that I got reviewed for 0.4 didn’t make the cut.  It was mainly due to my not testing and having a few bugs.  I’m currently working out the bugs and writing tests this weekend for it.  You can keep up with what the 3d squad will be releasing for 0.5 by clicking here.  Now that is a plan to integrate our work and make sure combining it goes smoothly.  Hopefully, it works.  I’ll let you know next week, if not sooner!


Continuing my journey in Open Source…

Just starting OSD700 and I’m a week behind already.  Luckily, the 0.4 release (which is out at the end of this week) involves more review than adding new functions.  We’ve also added some new members to the team… Tiago Moreira, who will be the project manager and release driver.  The other new member is Corban Brooks, who will act as another reviewer to help take the load off Al (aka F1LT3R).

Project Plan for OSD700

My project plan has already shifted.  I was initially going to try to tie up loose ends in my code and re-release my 0.3 code.  However, the group goal for 0.4 is to iron out previous code that may already be approved and put into the library.  So we’re starting a peer-review process and making the check-in process more efficient.  This will help future releases.  So, as far as the 0.4 release goes… there’s not supposed to be any really new code (which means I should postpone my changes until 0.5).  This is somewhat good because my future functions (or trying to take future functions) we’re looking a little bleak.  Anyway on to unveiling my plans:

Release 0.4 – Peer Review and Check-in working code (make sure PMatrix3D gets in)
Release 0.5 – Adjust camera functions to include PMatrix3D and more efficient in-library functions.
Release 0.6 – Pick up matrix functions that Ed Sin (MinyXO) left off with and make sure they get checked in.
Release 0.7 – Finalize any problems with the camera/matrix functions and finish beginCamera and endCamera.
Release 0.8 – Fix and bugs with beginCamera and endCamera.
Release 0.9 – bug fixing?
Release 1.0 – more bug fixing?