search

evil-mad / robopaint

The software for your friendly painting robot kit!
127 stars 34 forks source link

2.0.0-Beta1 release checklist #237

Closed techninja closed 8 years ago

techninja commented 9 years ago

Making things... making things... Wait, shouldn't we release at some point? ...maybe, probably... Yes!

After nearly a year of making great strides with the latest experimental version, before we get ahead of ourselves with wacky new features (#234, #228). we need to get something out there. Here's the bare minimum checklist (mostly for me) to get out a Beta1 release.

... I think that's it? I can likely do the release before all the testing is done, but I suspect there's a couple edge case "stupid level" errors still lurking in there as I test directly with the bot and brush so rarely.

EDIT: Almost forgot! Translation beyond English is a bit bungled. TONS of strings were added/edited/removed and thus the other languages have.. languished a bit. To make matters worse, google blocked me from (mis)using the tranlation API a bit. I have a hunch that @docprofsky wanted to do something with it, but I'm not sure how committed he is. If anything, most of the translations we setup will be fine, but anything missing will just have the English words/phrase in there.

techninja commented 9 years ago

Initial testing has gone well, but I've run into a snag on canvas paths that needs to be worked through. Good news is the various fill/stroke settings and styles add a lot of great style adjustment and seem to work pretty darn well!

techninja commented 9 years ago

Testing done (enough), I found a VERY longstanding bug in CNC Server where the draw speed was ignored, and squashed it flat! Also extra paths were being added to fills outside of the draw canvas, and that's been removed, so everything paints beautifully and incredibly smoothly. Tests with previous killers have also gone quite well.

techninja commented 9 years ago

One last tidbit remains.... and it seems zeroing is effectively broken. Well, at least in any clear cut use case involving streamlined buffers, as it requires at its time of calling that no other items be in the buffer. Once I get this worked out and upstreamed, we'll be ready to go.

techninja commented 9 years ago

Done. Building and writing release notes is now the name of the game!

oskay commented 9 years ago

w00t!

techninja commented 9 years ago

@oskay FWIW, Mac 2.0.0-Beta.1 is in the draft release right now. I'm not sure how you're going to sign it besides acting directly within the DMG (it is a drive image). We may need to modify the grunt mac build process to add in signing... though the builder has support to do it, I haven't added anything. See if you can't figure something out while I get the release notes and Lin/Win versions up there.

techninja commented 9 years ago

Linux is probably fine, but Windows is a priority, and our stopgap solution with the npm cull completely breaks the electron build. Sooo.... I'm currently battling the NPM 3 build dragon and hopefully I'll win. If anything, I can just release 2.0.0-Beta.1 as Mac only for the moment. Feh, and I was going to have this out today! :(

techninja commented 9 years ago

I've officially fixed/added since the "half" released version:

These will be in the "full" beta 1 release, when I get it all working.

Still battling:

techninja commented 9 years ago

Windows: As "stable" as node v5 may be, npm 3.3.6 is barfing all over a standard RoboPaint install. Master works, the paperjs branch does not. I've cut my losses and tried flatten again, and it appears to work, but now the app goes straight to black screen, I suspect path handling may be the culprit, but something wacky is going on. COuld also be Win 10 to blame, will test on Win7 as well.

Oh, and my Linux machine seems to have died. It's nearly 6 yrs old so.. I can't be too surprised :sob:

techninja commented 9 years ago

More Windowz Lulz: Turns out nothing at all is wrong with the app at all. Everything runs great without the bot plugged in. As soon as it is, BAM, it dies. Likely right during auto connection start. Neat thing is this means I can debug it directly. Will report back.

techninja commented 9 years ago

AHA! Found it, it was pretty serious. https://github.com/voodootikigod/node-serialport/pull/623 That giant version leap to 2.0 in node-serial wasn't for nothing and I'm left to assume a lot changed and needs a bit of testing. Guinea pigs are we I suppose. Seems quite happy now. Will move on with the beta1 release.

techninja commented 9 years ago

@oskay OK! Looks like all the issues have been worked out, and only ONE new one added :P

Sign the Mac build if you can, and we can publish the beta.

techninja commented 9 years ago

FWIW: A node-serialport maintainer called me on the above. Looks like a common bug so the wheel is squeaking a lot louder than just me :) https://github.com/voodootikigod/node-serialport/issues/610

techninja commented 8 years ago

@oskay Just rolled the latest Beta 1 attached to the original Beta release. Give that a test, a number of important show stopper bugs should be fixed... though I haven't been able to reproduce the blood taker, #250.

If this release is good enough for more testing by the populace, sign it, re-upload and I'll launch.

oskay commented 8 years ago

Testing looks OK so far. Now that we've made some progress, let's please roll #250 into this.

oskay commented 8 years ago

I have not met all of the testing requirements, but things appear to be working on the surface, and my short list of showstoppers have all been taken care of. Go?

oskay commented 8 years ago

Wait-- up to me, right? I'll see what I can do to figure out how to sign this DMG. ;)

oskay commented 8 years ago

Signed and uploaded!

techninja commented 8 years ago

WOO TEAMWORK!

giphy