Release Process Debrief - Revision history

BryceHarrington: /* Feedback from Users */

2017-08-10T01:17:47Z

Feedback from Users

← Older revision		Revision as of 01:17, 10 August 2017
Line 60:		Line 60:
	== Feedback from Users ==		== Feedback from Users ==
	* The usual questions about CMYK support. What's the status, what's the plan, can money be used effectively to further it, etc.		* The usual questions about CMYK support. What's the status, what's the plan, can money be used effectively to further it, etc.
			** http://codewideopen.blogspot.com/2009/12/inkscape-should-not-support-cmyk.html
	* Desire for an update on Mac package status. Strong desire for seeing native packaging. Various issues being encountered relating to current packaging systems.		* Desire for an update on Mac package status. Strong desire for seeing native packaging. Various issues being encountered relating to current packaging systems.


	== Other Ideas ==		== Other Ideas ==

BryceHarrington: /* Other Ideas */

2017-08-10T01:06:54Z

Other Ideas

← Older revision		Revision as of 01:06, 10 August 2017
Line 73:		Line 73:

	* Need to mark bugs in launchpad Fix Released that closed by 0.92.2		* Need to mark bugs in launchpad Fix Released that closed by 0.92.2

			* Part of the process for doing a release, should be to also set up the infrastructure for the next release
			** Add new milestones in Launchpad
			** Start a "desired bugs to fix" list to help focus efforts
			** Start a new Release_Notes page
			** Start a release checklist
			** Prep a kickoff email

BryceHarrington: /* Other Ideas */

2017-08-10T00:57:16Z

Other Ideas

← Older revision		Revision as of 00:57, 10 August 2017
Line 71:		Line 71:
	** https://gitlab.com/inkscape/inkscape-vectors/press/issues/1#note_37038992		** https://gitlab.com/inkscape/inkscape-vectors/press/issues/1#note_37038992
	** https://gitlab.com/inkscape/inkscape-vectors/press/issues/1#note_37063210		** https://gitlab.com/inkscape/inkscape-vectors/press/issues/1#note_37063210

			* Need to mark bugs in launchpad Fix Released that closed by 0.92.2

Moini: /* Other Ideas */

2017-08-10T00:52:12Z

Other Ideas

← Older revision		Revision as of 00:52, 10 August 2017
Line 65:		Line 65:
	== Other Ideas ==		== Other Ideas ==

	* The Vectors team needs a landing page to point prospective members at. Something that explains what the team is, how to join mattermost, and when the next meetup is scheduled, etc.		* The Vectors team needs a landing page to point prospective members at. Something that explains what the team is, how to join mattermost, and when the next meetup is scheduled, etc.
			** what about this one: https://inkscape.org/en/*inkscape-vectors? It can hold various documents for the team.

	* Vector Team's gitlab repo is partly private. Should it be?		* Vector Team's gitlab repo is partly private. Should it be?
	** https://gitlab.com/inkscape/inkscape-vectors/press/issues/1#note_37038992		** https://gitlab.com/inkscape/inkscape-vectors/press/issues/1#note_37038992
	** https://gitlab.com/inkscape/inkscape-vectors/press/issues/1#note_37063210		** https://gitlab.com/inkscape/inkscape-vectors/press/issues/1#note_37063210

Moini: /* Social Media */

2017-08-10T00:50:20Z

Social Media

← Older revision		Revision as of 00:50, 10 August 2017
Line 53:		Line 53:
	* We could use someone at the helm on Twitter. Ryan's responding to the bug reports with his personal Twitter account because he hates to see those go so long unaddressed.		* We could use someone at the helm on Twitter. Ryan's responding to the bug reports with his personal Twitter account because he hates to see those go so long unaddressed.
	* Worthwhile to do some organized recruitment. Maybe organizing a meetup would be good? Build a roster of 1-2 active posters on each media platform, and ask them to do the honors of posting our announcement?		* Worthwhile to do some organized recruitment. Maybe organizing a meetup would be good? Build a roster of 1-2 active posters on each media platform, and ask them to do the honors of posting our announcement?
	* We have influential VIP users with large followings on their blogs. E.g. the ~~Carrots~~ & ~~Peppers guy~~. Outreach to them might be worthwhile to get word of releases, fundraisers, etc. spread more broadly. Periodically touching base with these users to gather their input could be useful by itself.		* We have influential VIP users with large followings on their blogs. E.g. the Pepper & Carrot author. Outreach to them might be worthwhile to get word of releases, fundraisers, etc. spread more broadly. Periodically touching base with these users to gather their input could be useful by itself.

Moini: /* Website */

2017-08-10T00:47:20Z

Website

← Older revision		Revision as of 00:47, 10 August 2017
Line 29:		Line 29:

	== Website ==		== Website ==
	* The Release Notes pasted into the release tool are unformatted.		* <s>The Release Notes pasted into the release tool are unformatted.</s> Fixed for 0.92.2 by copy-pasting html from Wiki, fixed for future releases by addition of a WYSIWYG editor widget for entering the html.
	** It's possible to paste raw HTML in, but that seems hacky		** <s>It's possible to paste raw HTML in, but that seems hacky</s> Still possible, but also allows usage of js text editor now.
	** Markdown would be nice to have. Would need either a wiki->markdown script (e.g. modify mkNEWS), or even move Release Notes out of wiki to a markdown-based shared editing system. Need some deeper thinking on this...		** Markdown would be nice to have. Would need either a wiki->markdown script (e.g. modify mkNEWS), or even move Release Notes out of wiki to a markdown-based shared editing system. Need some deeper thinking on this...
	** At least, we need to be able to link Bug #'s to bug report URLs		*** Perhaps use a git repo, or even the respective Inkscape branch's git repo? Similar to a changelog? Make a template, and have a file for it that is relevant to the respective branch? Easy access for devs, no time lost converting to html for copy-pasting on website.
			** <s>At least, we need to be able to link Bug #'s to bug report URLs</s> Was possible for 0.92.2 already.
			** How should images be added to release notes? Currently, they need to be uploaded 'somewhere', and linked, e.g. from the Wiki. It would be nice to be able to upload them directly when adding to the text. That's a problem not only for the releases app, but also for the git option above.
	** Whatever we do, try to move in a direction of reducing/eliminating manual formatting effort		** Whatever we do, try to move in a direction of reducing/eliminating manual formatting effort

BryceHarrington: /* Scheduling */

2017-08-10T00:43:19Z

Scheduling

← Older revision		Revision as of 00:43, 10 August 2017
Line 18:		Line 18:
	* Objectively we're getting better at establishing and following a schedule, but for 0.92.2 there was still delays at the end. In each of 0.92.0, 0.92.1, and 0.92.2 the delays were caused by unique causes; something always piles up at the end and it's difficult to predict what it'll be.		* Objectively we're getting better at establishing and following a schedule, but for 0.92.2 there was still delays at the end. In each of 0.92.0, 0.92.1, and 0.92.2 the delays were caused by unique causes; something always piles up at the end and it's difficult to predict what it'll be.
	** When this happens, it is important to touch base with everyone in case someone is still working on something, to avoid a miscommunication leading to a premature announcement.		** When this happens, it is important to touch base with everyone in case someone is still working on something, to avoid a miscommunication leading to a premature announcement.

			* A roster of people to run through would be useful, keyed to the topic they're involved with. A LOT of people are involved in prepping a release, all important in various ways, and it's too easy to forget someone.
			** Contact early in cycle, "Is there anything you're concerned about for the upcoming release, that we need to account for?"
			** At pre0, contact again "How is <topic> coming along? Have you had a chance to make sure it's ready?" Make note of problem areas for followup.
			** Another touch point a day or so before the final tarball. "Is <topic> done?"
			** After the tarball but before the announcement is another touch point.

	== Packaging ==		== Packaging ==

TestaccountforSterbal: /* Social Media */

2017-08-10T00:28:41Z

Social Media

← Older revision		Revision as of 00:28, 10 August 2017
Line 46:		Line 46:
	* Worthwhile to do some organized recruitment. Maybe organizing a meetup would be good? Build a roster of 1-2 active posters on each media platform, and ask them to do the honors of posting our announcement?		* Worthwhile to do some organized recruitment. Maybe organizing a meetup would be good? Build a roster of 1-2 active posters on each media platform, and ask them to do the honors of posting our announcement?
	* We have influential VIP users with large followings on their blogs. E.g. the Carrots & Peppers guy. Outreach to them might be worthwhile to get word of releases, fundraisers, etc. spread more broadly. Periodically touching base with these users to gather their input could be useful by itself.		* We have influential VIP users with large followings on their blogs. E.g. the Carrots & Peppers guy. Outreach to them might be worthwhile to get word of releases, fundraisers, etc. spread more broadly. Periodically touching base with these users to gather their input could be useful by itself.


			Social media discussion is happening here: https://teams.freecreatives.org/inkscape

	== Feedback from Users ==		== Feedback from Users ==

BryceHarrington: /* Website */

2017-08-10T00:19:20Z

Website

← Older revision		Revision as of 00:19, 10 August 2017
Line 23:		Line 23:

	== Website ==		== Website ==
			* The Release Notes pasted into the release tool are unformatted.
			** It's possible to paste raw HTML in, but that seems hacky
			** Markdown would be nice to have. Would need either a wiki->markdown script (e.g. modify mkNEWS), or even move Release Notes out of wiki to a markdown-based shared editing system. Need some deeper thinking on this...
			** At least, we need to be able to link Bug #'s to bug report URLs
			** Whatever we do, try to move in a direction of reducing/eliminating manual formatting effort

	== Announcements ==		== Announcements ==

BryceHarrington: /* Other Ideas */

2017-08-10T00:15:42Z

Other Ideas

← Older revision		Revision as of 00:15, 10 August 2017
Line 48:		Line 48:

	== Other Ideas ==		== Other Ideas ==

	* The Vectors team needs a landing page to point prospective members at. Something that explains what the team is, how to join mattermost, and when the next meetup is scheduled, etc.		* The Vectors team needs a landing page to point prospective members at. Something that explains what the team is, how to join mattermost, and when the next meetup is scheduled, etc.

			* Vector Team's gitlab repo is partly private. Should it be?
			** https://gitlab.com/inkscape/inkscape-vectors/press/issues/1#note_37038992
			** https://gitlab.com/inkscape/inkscape-vectors/press/issues/1#note_37063210