Difference between revisions of "MacOS alpha"

From Inkscape Wiki
Jump to navigation Jump to search
Line 2: Line 2:
  
 
==Introduction==
 
==Introduction==
So you have been asked to participate in testing the Inkscape 1.0 alpha for macOS and you are willing to embark on this endeavor - great! Let me first thank you for your interest and give you "the tour" about what's up ahead.
+
So you have been (t)asked to participate in testing the Inkscape 1.0 alpha for macOS and you are willing to embark on this endeavor - great! Let me first thank you for your interest and give you "the tour" about what's up ahead.
  
 
===out with the old, in with the new===
 
===out with the old, in with the new===
Testing the 1.0 alpha for macOS will probably be a bit different from what you might expect: although Inkscape has been around for years and there have been official releases for macOS in the past, this app has undergone a lot more changes than "only" the leap from 0.9x codebase to 1.0 would lead you to think. It uses an entirely new build system (rebuilt from scratch and still being worked on) and that proves to be an additional source introducing issues and regressions until it's matured. So in addition to probably new/changed/broken/... functionalities originating from the 1.0 codebase there will be a lot of macOS-specific issues in Inkscape that none of the releases for the other platforms have. And these issues might be even of foundational nature; in fact, so foundational that you'd never expect them to surface in an app that already has years of development under its belt. To give you two examples, we've already had and fixed Inkscape crashing on opening/saving files as well as a broken text tool, accompanied by missing fonts and texts in a drawing...  I know that sounds bad and I know testing is not all fun and games, but we have to push through this once (and only once!), so please don't let that scare you off!
+
Testing the 1.0 alpha for macOS will probably be a bit different from what you might expect: although Inkscape has been around for years and there have been official releases for macOS in the past, this app has undergone a lot more changes than "only" the leap from 0.9x codebase to 1.0 would lead you to think. It uses an entirely new build system (rebuilt from scratch and still being worked on) and that proves to be an additional source introducing issues and regressions until it's matured. So in addition to probably new/changed/broken/... functionalities originating from the 1.0 codebase, there will be a lot of macOS-specific issues in Inkscape that none of the releases for the other platforms have. And these issues might be even of foundational nature; in fact, so foundational that you'd never expect them to surface in an app that already has years of development under its belt. To give you two examples, we've already had and fixed Inkscape crashing on opening/saving files as well as a broken text tool, accompanied by missing fonts and texts in a drawing...  I know that sounds bad and I know testing is not all fun and games, but we have to push through this once (and only once!), so please don't let that scare you off!
 +
 
 +
==Testing==
 +
There are many ways to approach this and you are free to do what you like (and we encourage you to do so), but let me give you two possibilities in case you are unsure how to get started.
 +
* Use Inkscape 1.0 alpha as if it was the final release. Do your drawings and what you regularly do, but use the alpha version for it. This way you will notice if something is different/broken/slower/... than you are used to because you are in familiar territory. But don't forget that this release is not production-ready, so save your work more often to not have your day ruined if something unexpected happens.
 +
* Just play around. Do things for fun, click through all the menus, go search for things that are new or that you have never used before. Make a copy of your most complex drawing you have ever done and open that copy in Inkscape alpha. Does it look like you would expect?
  
 
===early testing group===
 
===early testing group===
If you are part of the early testing group (you know who you are because you'll have been told), that is exactly why you are a small select group - we need to find the remaining foundational issues before we announce any kind of public testing, or else we'll get swamped with tickets and complaints. So you might have a more frustrating job than "regular" testers since you are likely the ones finding more big and obvious issues. You should be aware of (the importance of!) that so you don't get discouraged should you hit a dead end after the first five minutes and then having to wait a few days until it's fixed.
+
If you are part of the early testing group (you know if you are because you'll have been told), you are now crew members of the starship Enterprise: "to boldly go where noone has gone before". The releases you are about to test have not undergone any previous testing besides "draw a circle, a rectangle, add some text, save file". So not only are you probably going to see more bugs, you'll also (hopefully) encounter all the remaining foundational issues that would make Picard do the facepalm. For example, nobody has tested if printing still works. And these are the things we need to find out and fix before we announce any kind of public testing, or else we would get swamped with issues and complaints. Do not let it discourage you if you find major issues like that, it is important that you do. So be brave, put on your red shirt and join the away team! (Enough with the Star Trek references already!)
  
 
===regular testing group===
 
===regular testing group===
If you are part of the regular testing group (you know who you are because you won't have been told to be an early tester ;-)),the most obvious and frustrating issues that would stop you from working with Inkscape after a few minutes will hopefully have been found and fixed by the early testers. But that's no guarantee, though, so please don't get discouraged as well.
+
If you are part of the regular testing group (you know if you are because you have not been told to put on a red shirt...), some brave men and women have <s>sacrificed their sanity</s> already been testing the alpha releases before you. That does not mean that you won't find any bugs, but hopefully there won't be any major blockers left that would stop you from testing after 5 minutes. But still, no guarantees.  
  
  
 +
==Reporting issues==
  
(Example: the first working build crashed on File|Open or File|Save apologize for that, but that's something we have to push through with the new build system.
 
 
 
by a completely new build systemd system than before. And whenever you , y new due to a new build process.    And since there was/is no recipe out there that tells us everything upfront that we have to do to get it working, there will very likely be (a lot?) stuff left that is still broken and that we have yet to fix. And that is where you come in: we need you to use and test Inkscape intensively to verify everything works as expected. as if it were a regular release and tell us about all the issues you encounter.
 
 
At the same point, a lot of stuff d So there was/is a lot of research and trial & error involved until we finally get everything right. That means that there can and will be errors and issues that you wouldn't expect from a software that has been around for years and is finally making the leap to 1.0.
 
  
  
Line 34: Line 34:
  
 
===where to report===
 
===where to report===
 
 
 
The sections below go into detail about where you
 
This is where it's going to happen!
 

Revision as of 11:13, 5 May 2019

Template:Warning This page is work in progress and not to be used until this warning is being removed!

Introduction

So you have been (t)asked to participate in testing the Inkscape 1.0 alpha for macOS and you are willing to embark on this endeavor - great! Let me first thank you for your interest and give you "the tour" about what's up ahead.

out with the old, in with the new

Testing the 1.0 alpha for macOS will probably be a bit different from what you might expect: although Inkscape has been around for years and there have been official releases for macOS in the past, this app has undergone a lot more changes than "only" the leap from 0.9x codebase to 1.0 would lead you to think. It uses an entirely new build system (rebuilt from scratch and still being worked on) and that proves to be an additional source introducing issues and regressions until it's matured. So in addition to probably new/changed/broken/... functionalities originating from the 1.0 codebase, there will be a lot of macOS-specific issues in Inkscape that none of the releases for the other platforms have. And these issues might be even of foundational nature; in fact, so foundational that you'd never expect them to surface in an app that already has years of development under its belt. To give you two examples, we've already had and fixed Inkscape crashing on opening/saving files as well as a broken text tool, accompanied by missing fonts and texts in a drawing... I know that sounds bad and I know testing is not all fun and games, but we have to push through this once (and only once!), so please don't let that scare you off!

Testing

There are many ways to approach this and you are free to do what you like (and we encourage you to do so), but let me give you two possibilities in case you are unsure how to get started.

  • Use Inkscape 1.0 alpha as if it was the final release. Do your drawings and what you regularly do, but use the alpha version for it. This way you will notice if something is different/broken/slower/... than you are used to because you are in familiar territory. But don't forget that this release is not production-ready, so save your work more often to not have your day ruined if something unexpected happens.
  • Just play around. Do things for fun, click through all the menus, go search for things that are new or that you have never used before. Make a copy of your most complex drawing you have ever done and open that copy in Inkscape alpha. Does it look like you would expect?

early testing group

If you are part of the early testing group (you know if you are because you'll have been told), you are now crew members of the starship Enterprise: "to boldly go where noone has gone before". The releases you are about to test have not undergone any previous testing besides "draw a circle, a rectangle, add some text, save file". So not only are you probably going to see more bugs, you'll also (hopefully) encounter all the remaining foundational issues that would make Picard do the facepalm. For example, nobody has tested if printing still works. And these are the things we need to find out and fix before we announce any kind of public testing, or else we would get swamped with issues and complaints. Do not let it discourage you if you find major issues like that, it is important that you do. So be brave, put on your red shirt and join the away team! (Enough with the Star Trek references already!)

regular testing group

If you are part of the regular testing group (you know if you are because you have not been told to put on a red shirt...), some brave men and women have sacrificed their sanity already been testing the alpha releases before you. That does not mean that you won't find any bugs, but hopefully there won't be any major blockers left that would stop you from testing after 5 minutes. But still, no guarantees.


Reporting issues

Downloads

todo You'll find the most recent builds ...

Please take note what exact build you are testing because we will be talking about which build has which issues and in which build it is supposed to be fixed. Should you at some point have forgotten or it just got messy and confusing, you can find and use the version number in the "About" dialog as it shows the exact Git commit as well.

Reporting issues

The ideal issue report

where to report