Full time entrepreneur. Develover and contributor at Netbeast. Telecommunications engineering, image & sound branch at University of Seville. Linux systems administrator, Shell and JavaScript programmer, Raspberry Pi and router firmware designer."Techie". Photography and image processing lover. Keen on learning new things and teaching others those that I know.
Experience: Linux administrator system, ShellScript, JavaScript, NodeJs,HTML,CSS,Photoshop,Office, Marketing Strategies, SEM, RaspberryPi, Wifi Network, Programming of low level devices, Git, Blogs.
Nothing here yet.
No blogs yet.
From their website: "Private repositories are just like public ones. However, it isn’t possible to browse them or search their content on the public registry. They do not get cached the same way as a public repository either."
As @whotheheck said, electron is one of the best ways to create binaries for windows, mac and linux. After using electron to create the binary, you can use electron-packager to create .exe and .dmg. I have used that for this project Netbeast . You can take a look on the README to see how I did it ;)
It depends on which branch are you working at and also about your product itself. If you are working on a really crucial feature or you are solving a bug or a security problem you will probably create a branch make a pull request and then merge it. However if you are working on a improvement I would wait to have the minimum viable product and then merge it.
If that task is mandatory and necessary to keep going on the project you should create another due date for that task. Also ask for help to finish that task before time is over. Next time take this experience into account before estimating a date for a milestone.