Author Topic: Finishing up the final pieces  (Read 14615 times)

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Finishing up the final pieces
« Reply #30 on: January 05, 2013, 01:03:26 AM »
All set up and ready to go for BugSense.  We can send arbitrary key-value pairs, though long strings will need to be broken into chunks.  The key missing feature is logcat; ACRA will send it in the report, but BugSense won't display it.  Fortunately we can attach ACRA to another (or multiple) backends later if we want.

Check out the dashboard to see some example errors.  It's easy to "resolve" (hide) errors but I can't figure out how to completely delete old reports (maybe they just have to expire out).  If you look at some of the resolved errors you'll see all the gobs of information that gets passed in the default ACRA report - some potentially sensitive.  So I removed that chunk of the report.

I still have to update the About menuitem, but otherwise it's ready for the next snapshot build.  I guess we'll call it 2.a.0.  You probably know this already, but if we bump the version code to 16, users won't be able to install older snapshots without completely uninstalling.  So maybe we keep it at 15 throughout alpha.  Then bump it to 16 for beta.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Finishing up the final pieces
« Reply #31 on: January 05, 2013, 09:11:43 PM »
Just added the "About" dialog.  Earlier today I put in a controller diagnostics screen.  For awhile now I've been using a little app I wrote to test controller signals and help debug.  It finally occurred to me that I could just drop this into Mupen as another activity, with almost no change to the code.  So I put it into the Advanced menu.  Should make it easier to work through controller issues now.

My plate is pretty much clean now.  I'll start looking at the CRC header thing you mentioned a few posts back, unless there's something more urgent.
« Last Edit: January 05, 2013, 10:14:00 PM by littleguy »
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3496
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Finishing up the final pieces
« Reply #32 on: January 06, 2013, 12:47:55 AM »
Do you think the menu strings are likely to be stable now, or any expected changes before publishing?  I should start getting translators involved if were are at a good point for that now.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Finishing up the final pieces
« Reply #33 on: January 06, 2013, 12:58:15 AM »
I think the ones that are there are pretty much set.  I seem to keep adding more with each new feature though  :P. I kind of think translation should occur at the end of the beta.  I'm sure as we getnmore testers we'll continue to update stuff based on feedback.  But if you're eager to proceed I guess it's fine.  It does become a maintenance chore if things are still in flux...
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Finishing up the final pieces
« Reply #34 on: January 06, 2013, 01:28:30 PM »
Important note: I moved the default game save location from <sd>/GameSaves to <sd>/mupen64plus.  I thought this would be most obvious to users what the contents pertain to, and it's a familiar pattern that a lot of apps use.

For the next snapshot, testers should be made aware of a few important things:
 - They should revert to the default settings
 - They will need to rename their gamesave folder (if they've been using the default) or update the location inside mupen.
 - They can start posting bugs/issues/ideas to github, which they can access from the help menu in mupen64plus.

2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Finishing up the final pieces
« Reply #35 on: January 07, 2013, 09:10:32 AM »
Ok, sorry for all the posts.  Just wanted to summarize my suggestions for the next snapshot since a lot has changed:

 - Bump manifest version info to "2.a.0"
 - Start a new thread, call it "Alpha testing" or something
    + Link to latest build
    + Testers can help by
         * reporting bugs using the Help menu on the main screen (also provide direct link)
         * enabling crash reporting in the Advanced menu
    + For controller issues, testers should
         * use the diagnostics screen in the Advanced menu
         * report their observations in a bug report
    + Start a changelog in the second post
         * I'm happy to maintain it if you give me write privileges to that post
 - Update the first post of the snapshots thread saying
    + Alpha testing has begun, point to new thread
    + Current snapshot users should
          * reset to the default settings after updating
          * rename their gamesave folder to 'mupen64plus' (if they've been using the default)
          * or update the gamesave location in the Advanced menu as necessary
    + Consider removing snapshot links in a month or two when they're no longer needed
 - Update the last post of the snapshots thread so that subscribed users are notified
« Last Edit: January 07, 2013, 09:46:28 AM by littleguy »
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3496
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Finishing up the final pieces
« Reply #36 on: January 07, 2013, 11:41:41 AM »
Ok, but I think instead of "Alpha Testing" (as that could get confusing to folks looking back later on, considering there was already an Alpha Testing phase), instead I will call it "Beta 2.0 Release Candidates".  This will be the final lead-up to the published app.  I think I said that before, but this time we really are very close to the point where we can publish.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Finishing up the final pieces
« Reply #37 on: January 07, 2013, 12:06:36 PM »
Maybe I should have asked how many phases before releasing to market.

If this is the last phase of testing before release, I would use either the term "Beta" or "Release Candidate" but not both, since in my experience those are distinctly different things.  If this is the last phase, I would probably use the term "Beta 2.0" and skip right to release (we're not developing an operating system ;D).  Or let Wikipedia be your guide:
http://en.wikipedia.org/wiki/Software_release_life_cycle

Any way you slice it, I'm looking forward to the next release!

Edit: Of course in the subtext of the thread you could use the term "release candidate" to emphasize the nearness to release.  I'm just saying pick Beta or Release Candidate as the official name.  Ok I'll shut up now...
« Last Edit: January 07, 2013, 12:19:38 PM by littleguy »
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3496
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Finishing up the final pieces
« Reply #38 on: January 07, 2013, 12:24:40 PM »
Good point, since the Beta will not actually be until it is released (kind of redundant).  My thinking was "these are candidate builds for release as Beta 2.0", but of course that is too long of a title for anyone to want to read :)
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Finishing up the final pieces
« Reply #39 on: January 07, 2013, 12:32:43 PM »
"these are candidate builds for release as Beta 2.0"

To me that is the definition of Alpha, and to avoid confusion just say Alpha 2.0.  It's not at all uncommon to Alpha test when the major version number changes.  Alpha implies "lots of bugs" "incomplete features" "use at your own risk" "don't expect the world" and "I'm not formally testing the product yet, but you're welcome to take a peek and offer feedback".

Edit: Really it's just about managing tester expectations.  If you use Beta or RC when the software is only Alpha level, people can get pissed when they discover all the missing features and major flaws (or lose their data!)
« Last Edit: January 07, 2013, 12:38:02 PM by littleguy »
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3496
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Finishing up the final pieces
« Reply #40 on: January 07, 2013, 12:56:38 PM »
The actual release will not be perfect, though.  Anyone following the project will be used to that, and I'll handle the nasty emails from those who aren't.  I published Beta 1.0 much more broken than what we have now.  To me, Alphas were what I'd call the snapshot builds, and now we are ready to publish and just need to do stress tests to catch anything major with the crash reports or something.  The thing that muddles this update compared to previous ones is that we are struggling very hard to not regress anything that was working in 1.9.2, so I see where you are coming from.  However, I don't want a long protracted Alpha testing phase -- I feel like we are at a good point to publish now, with maybe a few more bugs squashed first.  I'd really like to publish this coming weekend if humanly possible, and push some quick updates the following week to address any big concerns.  After that I'll be focusing almost exclusively on the Open Pandora and OUYA ports.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Finishing up the final pieces
« Reply #41 on: January 07, 2013, 01:04:07 PM »
Cool!  Now I see how you came up with the name Beta 2.0 RC - because you are releasing the beta!  Duh.  In the announcement I would just say Version 2.0 Release Candidate... should be clear enough to testers, and communicates nearness to release.  Then publish as Beta ;)
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Finishing up the final pieces
« Reply #42 on: January 07, 2013, 01:08:08 PM »
Oh, maybe a good time to list the features in 1.9.2 that still need hookup in 2.0.  Other than special funcs, I can't think of anything off the top of my head.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3496
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Finishing up the final pieces
« Reply #43 on: January 07, 2013, 01:17:26 PM »
Will do.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline zack

  • Developer
  • byte
  • *****
  • Posts: 36
    • View Profile
    • InfuseDreams
Re: Finishing up the final pieces
« Reply #44 on: January 08, 2013, 03:45:49 AM »
Just an fyi. I am going to start digging into the code this weekend, and have decided to take a look at our rice plugin first to see what improvements can be made there. Fog I know is one.

I believe that is the most compatible plugin so I feel that should be the one focused on.