Looking for Beta-testers!

MichMich

To improve and guarantee the quality of themaster releases, it’s important that the develop branch is thoroughly tested before it’s merged into master. Because of this, I’m looking for beta testers that are willing to test the develop branch before I release it as master.

If you are interested, please subscribe to this topic so you will be notified if a new develop version is ready to be tested.

As we speak, a development version is ready to be tested. To switch to the development branch, please execute the following commands:

cd ~/MagicMirror
git checkout --track origin/develop

If you run into any issues, please let me know.

Note: comments not related to testing (So asking help for issues that are not caused by a develop change) will be deleted to keep this post clean.

KirAsh4

You mean I shouldn’t, by default, be living on the edge and always use the develop branch? :)

MichMich

@KirAsh4 Yes, you should.

KirAsh4

LOL!

Seriously folks, we do need people to test out the develop code. It’s one thing for us to write code and push it up and only a select few test it, particularly those who have asked for that bit of code. We need the greater population to test as well. Something may be broken for others, or we may have inadvertently broken existing code and we won’t know.

So please, test the code, let us know what works, what doesn’t, what fails. It’s the only way we can find these bugs.

d3r

This would be a separate install, right?

pigreco

hello guys,

just registered and quite new on the forum…
I really appreciate your work and i have already used the code to create my first prototype (with film at the moment waiting for a nice real mirror, i will try to post some photos).
I am using a 10.1 inch screen (ultra thin) with a PI3.
I will try to help you guys as a beta tester and if you want i would like also to discuss about new ideas.

Kr
Pi

KirAsh4

@d3r, if you checkout the code as per @MichMich’s instructions above, it will automatically download and over write the current codebase with the develop branch. It will NOT overwrite your current config.js file.

KirAsh4

@pigreco, feel free to post your ideas in the various sections they might pertain to, modules, core system, or a general topic.

kckndrgn

Cool, I’m in, I like breaking things LOL :D

As a noob to the MM project I’m really fascinated by it and eager to start writing my own modules (though I keep finding modules that suit my purpose).

pigreco

Hello guys,

i have tried to pass to development branch but i got this error

error: Your local changes to the following files would be overwritten by checkout:
modules/default/clock/clock.js
Please, commit your changes or stash them before you can switch branches.
Aborting

I suppose that was due to my code change on the second colour of the analog clock in the module clock.js…i had just put the red colour #FF0000…i have retested with the @ #888888 one but still the same error…

A possible bug?

Cheers
Pi

MichMich

@pigreco, no this is the expected result. GIT doesn’t want to overwrite your changes. This is why you should never make ani modifications to the modules or the core files. If you want to modify the design, you can use the css/custom.css file (this file will be ignored by git).

To remove your changes so that you can update continue, please use: git stash

pigreco

Hello @MichMich thanks for the suggestion…not very familiar with stash, i need to authenticate ?

Thanks
PI

MichMich

@pigreco You could also try:

git fetch origin
git reset --hard origin/develop
git clean -f

pigreco

Thanks @MichMich …the issue is solved…i am on the develop branch :-)

dejayou

This post is deleted!

KirAsh4

@pigreco, I didn’t expose the other clock hands to be easily accessible to change the colors on. I’ll have to add that in in a later update. As @MichMich said, making changes to those core files will cause git to start complaining at you.

bscarano

I’m now on Develop. Will this update automatically or will I need to run something periodically?

KirAsh4

@bscarano, regardless of which branch you are on, you are in charge of your mirror, including updating the code.

MichMich

@bscarano To update to the latest version, you’ll need to pull the latest changes. This can be done using: git pull (from the command line within your MagicMirror² folder).

kckndrgn

I am now on the development branch.
I have verified that the changes fixed my “blank screen” with the language set in the config file.

Thanks!