MacOS alpha - Revision history

Speleo3: fix link

2019-09-05T18:08:57Z

fix link

← Older revision		Revision as of 18:08, 5 September 2019
Line 7:		Line 7:
	\|-		\|-
	!style="vertical-align: top"\| Issues:		!style="vertical-align: top"\| Issues:
	\| <ul><li>[https://gitlab.com/inkscape/inkscape/issues/183 Summary]<li>[https://gitlab.com/groups/inkscape/-/issues?label_name%5B%5D=OS::~~Mac~~ Known issues]<li>[https://inkscape.org/contribute/report-bugs/ Report issues]</ul>		\| <ul><li>[https://gitlab.com/inkscape/inkscape/issues/183 Summary]<li>[https://gitlab.com/groups/inkscape/-/issues?label_name%5B%5D=OS::macOS Known issues]<li>[https://inkscape.org/contribute/report-bugs/ Report issues]</ul>
	\|-		\|-
	! Chat		! Chat

Speleo3: scoped label

2019-07-11T21:26:57Z

scoped label

← Older revision		Revision as of 21:26, 11 July 2019
Line 7:		Line 7:
	\|-		\|-
	!style="vertical-align: top"\| Issues:		!style="vertical-align: top"\| Issues:
	\| <ul><li>[https://gitlab.com/inkscape/inkscape/issues/183 Summary]<li>[https://gitlab.com/groups/inkscape/-/issues?label_name%5B%5D=OS~~%2FMac~~ Known issues]<li>[https://inkscape.org/contribute/report-bugs/ Report issues]</ul>		\| <ul><li>[https://gitlab.com/inkscape/inkscape/issues/183 Summary]<li>[https://gitlab.com/groups/inkscape/-/issues?label_name%5B%5D=OS::Mac Known issues]<li>[https://inkscape.org/contribute/report-bugs/ Report issues]</ul>
	\|-		\|-
	! Chat		! Chat

Dehesselle: Add link to "how to report an issue"-video

2019-06-17T17:24:00Z

Add link to "how to report an issue"-video

← Older revision		Revision as of 17:24, 17 June 2019
Line 56:		Line 56:

	==Reporting issues==		==Reporting issues==
	Now comes the part where "fun" turns a bit into "work". If you found an issue, we need you to tell us about it so we can fix it. Please go to https://inkscape.org/report and use the search function first to see if anyone else has already reported it. If there is already an issue, comment and add to it. If not, create a new one.		Now comes the part where "fun" turns a bit into "work". If you found an issue, we need you to tell us about it so we can fix it. Please go to https://inkscape.org/report and use the search function first to see if anyone else has already reported it. If there is already an issue, comment and add to it. If not, create a new one. There's also an introductory [https://inkscape.org/news/2019/02/02/step-step-video-launched-how-report-issue-inkscape/ video] to help you through the process.

	Basically, it comes down to these (more details available in https://inkscape.org/contribute/report-bugs/):		Basically, it comes down to these (more details available in https://inkscape.org/contribute/report-bugs/):

Speleo3: quick links

2019-05-30T20:30:07Z

quick links

← Older revision		Revision as of 20:30, 30 May 2019
Line 1:		Line 1:
			{\| cellspacing="0" cellpadding="3" style="float: right; width: 30em; border: 1px solid #99f; background-color: #eee; text-align: left"
			\|-
			!colspan="2" style="text-align:center; background-color: #99f"\| Quick Links
			\|-
			!style="vertical-align: top"\| Download:
			\| Artifacts from latest "inkscape:mac" CI job:<br>https://gitlab.com/inkscape/inkscape/-/jobs
			\|-
			!style="vertical-align: top"\| Issues:
			\| <ul><li>[https://gitlab.com/inkscape/inkscape/issues/183 Summary]<li>[https://gitlab.com/groups/inkscape/-/issues?label_name%5B%5D=OS%2FMac Known issues]<li>[https://inkscape.org/contribute/report-bugs/ Report issues]</ul>
			\|-
			! Chat
			\| https://chat.inkscape.org/channel/team_devel_mac
			\|}

	==Introduction==		==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! Thank you for your interest and the time you will be spending helping us out. Let me give you "the tour" about what's up ahead so you know what you'll be getting yourself into.		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! Thank you for your interest and the time you will be spending helping us out. Let me give you "the tour" about what's up ahead so you know what you'll be getting yourself into.

Dehesselle: add link to contribute/report-bugs

2019-05-07T22:05:19Z

add link to contribute/report-bugs

← Older revision		Revision as of 22:05, 7 May 2019
Line 44:		Line 44:
	Now comes the part where "fun" turns a bit into "work". If you found an issue, we need you to tell us about it so we can fix it. Please go to https://inkscape.org/report and use the search function first to see if anyone else has already reported it. If there is already an issue, comment and add to it. If not, create a new one.		Now comes the part where "fun" turns a bit into "work". If you found an issue, we need you to tell us about it so we can fix it. Please go to https://inkscape.org/report and use the search function first to see if anyone else has already reported it. If there is already an issue, comment and add to it. If not, create a new one.

			Basically, it comes down to these (more details available in https://inkscape.org/contribute/report-bugs/):
	* What macOS and Inkscape version are you using?		* What macOS and Inkscape version are you using?
	* What is the problem you encountered? Describe it in as much detail as you see fit. (Only one problem per issue please!)		* What is the problem you encountered? Describe it in as much detail as you see fit. (Only one problem per issue please!)

Dehesselle: slight rephrasing as questions for more uniformity

2019-05-05T21:30:41Z

slight rephrasing as questions for more uniformity

← Older revision		Revision as of 21:30, 5 May 2019
Line 44:		Line 44:
	Now comes the part where "fun" turns a bit into "work". If you found an issue, we need you to tell us about it so we can fix it. Please go to https://inkscape.org/report and use the search function first to see if anyone else has already reported it. If there is already an issue, comment and add to it. If not, create a new one.		Now comes the part where "fun" turns a bit into "work". If you found an issue, we need you to tell us about it so we can fix it. Please go to https://inkscape.org/report and use the search function first to see if anyone else has already reported it. If there is already an issue, comment and add to it. If not, create a new one.

	* macOS ~~version~~ and Inkscape version		* What macOS and Inkscape version are you using?
	* What is the problem you encountered? Describe it in as much detail as you see fit. (Only one problem per issue please!)		* What is the problem you encountered? Describe it in as much detail as you see fit. (Only one problem per issue please!)
	* Is it reproducible and can you list the steps in order to reproduce it?		* Is it reproducible and can you list the steps in order to reproduce it?
	* Can you supply a <code>demo.svg</code> to demonstrate the issue if necessary (i.e. not easily reproducible by other means)?		* Can you supply a <code>demo.svg</code> to demonstrate the issue if necessary (i.e. not easily reproducible by other means)?
	* ~~whatever~~ you find ~~important~~ in context of the issue		* What else do you find worth mentioning in context of the issue?

	Your feedback and the time you put into it is greatly appreciated. It helps making Inkscape better for everyone. Every issue will be read and answered, but it might take us some time to get around. So please be patient if you don't get a response immediately and rest assured that your work is valuable and that you will hear from us.		Your feedback and the time you put into it is greatly appreciated. It helps making Inkscape better for everyone. Every issue will be read and answered, but it might take us some time to get around. So please be patient if you don't get a response immediately and rest assured that your work is valuable and that you will hear from us.

Moini: /* Out with the old, in with the new */

2019-05-05T21:08:27Z

Out with the old, in with the new

← Older revision		Revision as of 21:08, 5 May 2019
Line 3:		Line 3:

	===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 ([[Release_notes/1.0 \| see release notes draft]]), 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 ([[Release_notes/1.0 \|see release notes draft]]), 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==		==Testing==

Moini: /* Out with the old, in with the new */

2019-05-05T21:07:59Z

Out with the old, in with the new

← Older revision		Revision as of 21:07, 5 May 2019
Line 3:		Line 3:

	===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 ([[Release_notes/1.0 \| see release notes draft]]), 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==		==Testing==

Moini at 21:05, 5 May 2019

2019-05-05T21:05:36Z

← Older revision		Revision as of 21:05, 5 May 2019
Line 37:		Line 37:
	[[File:macos_alpha_quicklook_version.png]]		[[File:macos_alpha_quicklook_version.png]]

	===~~about~~ Inkscape.app===		===About Inkscape.app===
	* The app is not signed. You have to <code>[right-click][Open]</code> the app due to Gatekeeper complaining about an unverified developer. (We're working on it!)		* The app is not signed. You have to <code>[right-click][Open]</code> the app due to Gatekeeper complaining about an unverified developer. (We're working on it!)
	* Inkscape no longer requires X11, but proper macOS integration like the menubar is still on the todo list.		* Inkscape no longer requires X11, but proper macOS integration like the menubar is still on the todo list.
Line 54:		Line 54:
	Thank you!		Thank you!

	==~~contact~~==		==Contact==
	If you have further questions about the macOS alpha test, there's https://chat.inkscape.org where we regularly hang out in <code>#team_devel_mac</code>.		If you have further questions about the macOS alpha test, there's https://chat.inkscape.org where we regularly hang out in <code>#team_devel_mac</code>.

Moini: /* Testing */

2019-05-05T21:02:05Z

Testing

← Older revision		Revision as of 21:02, 5 May 2019
Line 13:		Line 13:
	Generally speaking, the more you use and spend time with the alpha, the better. No one alone can and will find every bug, it's the joint effort of different people with different usage scenarios and different needs that will allow us to cover as much (testing-) ground as possible.		Generally speaking, the more you use and spend time with the alpha, the better. No one alone can and will find every bug, it's the joint effort of different people with different usage scenarios and different needs that will allow us to cover as much (testing-) ground as possible.

	===~~early~~ testing group===		===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!)		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 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.		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.

	==Downloading==		==Downloading==