Pre-release checklist - Гісторыя версій

Een на 11:57, 19 кастрычніка 2020

2020-10-19T11:57:58Z

← Папярэдн. версія		Версія ад 13:57, 19 кастрычніка 2020
Радок 43:		Радок 43:
	** Create a build for your game from the "manage game" page (using the '''Build a new release version''' section) and check the log to make sure that everything builds fine (after a successful build, you should see a new version in "Versions available for production").		** Create a build for your game from the "manage game" page (using the '''Build a new release version''' section) and check the log to make sure that everything builds fine (after a successful build, you should see a new version in "Versions available for production").
	** Send an e-mail to studio@boardgamearena.com asking to move the project forward for review. You cannot deploy yourself from the "manage game" page until a first deploy has been done by the admins. Please note that '''everything must be OK on the licensing''' side for a project to be moved to production.		** Send an e-mail to studio@boardgamearena.com asking to move the project forward for review. You cannot deploy yourself from the "manage game" page until a first deploy has been done by the admins. Please note that '''everything must be OK on the licensing''' side for a project to be moved to production.
	** When admins publish (push to alpha) they will send an email to the developer with all relevant information about next steps.		** When admins publish (push to alpha) they will send an email to the developer with all relevant information about the next steps.

Victoria La на 18:16, 12 кастрычніка 2020

2020-10-12T18:16:48Z

← Папярэдн. версія		Версія ад 20:16, 12 кастрычніка 2020
Радок 31:		Радок 31:
	* User Interface		* User Interface
	** Review BGA UI design Guidelines [[BGA_Studio_Guidelines]]		** Review BGA UI design Guidelines [[BGA_Studio_Guidelines]]
			** Check all your english message for proper use of punctuation, capitalization, usage of present tense in notification (not past) and gender nuturality. See [[Translations]] for English rules.
	** If the elements in your game zone don't occupy all the available horizontal space, '''they should be centered'''.		** If the elements in your game zone don't occupy all the available horizontal space, '''they should be centered'''.
	** If your game elements become blurry or pixellated when using the browser zoom, you ~~forgot~~ to ~~use~~ [[Game_art:_img_directory#Use_background-size \| higher resolution images with background-size]]		** If your game elements become blurry or pixellated when using the browser zoom, you may want to consider [[Game_art:_img_directory#Use_background-size \| higher resolution images with background-size]]
	** Non-self explanatory graphic elements should have tooltips		** Non-self explanatory graphic elements should have tooltips
	** If graphic elements appear in notification log they should have titles (i.e. title attribute of div) so can be read in non rendered form (i.e. as text only)		** If graphic elements appear in notification log they should have titles (i.e. title attribute of div) so can be read in non rendered form (i.e. as text only)

Victoria La на 18:00, 11 кастрычніка 2020

2020-10-11T18:00:26Z

← Папярэдн. версія		Версія ад 20:00, 11 кастрычніка 2020
Радок 38:		Радок 38:
	** A prefix for example a trigram for your game that you append to all the css classes to avoid namespace conflicts, i.e. vla_selected vs selected		** A prefix for example a trigram for your game that you append to all the css classes to avoid namespace conflicts, i.e. vla_selected vs selected
	** If you are looking for advice on design and some 3rd party testing you can post a message on the developers forum, and ask other developers, there are a lot of people who will gladly do it.		** If you are looking for advice on design and some 3rd party testing you can post a message on the developers forum, and ask other developers, there are a lot of people who will gladly do it.
	* Finally move to Alpha ~~stage~~		* Finally move to Alpha status
	** If possible (meaning if there is not already a project with that name) copy your project to a new project '''matching exactly the name of the game''' (no prefix or suffix). If not possible move on to the next steps, admin will have to retrieve the other project and overwrite it.		** If possible (meaning if there is not already a project with that name) copy your project to a new project '''matching exactly the name of the game''' (no prefix or suffix). If not possible move on to the next steps, admin will have to retrieve the other project and overwrite it.
	** Create a build for your game from the "manage game" page (using the '''Build a new release version''' section) and check the log to make sure that everything builds fine (after a successful build, you should see a new version in "Versions available for production").		** Create a build for your game from the "manage game" page (using the '''Build a new release version''' section) and check the log to make sure that everything builds fine (after a successful build, you should see a new version in "Versions available for production").
	** Send an e-mail to studio@boardgamearena.com asking to move the project forward for review. You cannot deploy yourself from the "manage game" page until a first deploy has been done by the admins. Please note that '''everything must be OK on the licensing''' side for a project to be moved to production.		** Send an e-mail to studio@boardgamearena.com asking to move the project forward for review. You cannot deploy yourself from the "manage game" page until a first deploy has been done by the admins. Please note that '''everything must be OK on the licensing''' side for a project to be moved to production.
	** When admins publish (push to alpha) they will send an email to the developer with all relevant information about next steps.		** When admins publish (push to alpha) they will send an email to the developer with all relevant information about next steps.

Victoria La на 17:55, 11 кастрычніка 2020

2020-10-11T17:55:45Z

← Папярэдн. версія		Версія ад 19:55, 11 кастрычніка 2020
Радок 41:		Радок 41:
	** If possible (meaning if there is not already a project with that name) copy your project to a new project '''matching exactly the name of the game''' (no prefix or suffix). If not possible move on to the next steps, admin will have to retrieve the other project and overwrite it.		** If possible (meaning if there is not already a project with that name) copy your project to a new project '''matching exactly the name of the game''' (no prefix or suffix). If not possible move on to the next steps, admin will have to retrieve the other project and overwrite it.
	** Create a build for your game from the "manage game" page (using the '''Build a new release version''' section) and check the log to make sure that everything builds fine (after a successful build, you should see a new version in "Versions available for production").		** Create a build for your game from the "manage game" page (using the '''Build a new release version''' section) and check the log to make sure that everything builds fine (after a successful build, you should see a new version in "Versions available for production").
	** Send an e-mail to studio@boardgamearena.com asking to move the project forward for review. You cannot deploy yourself from the "manage game" page until a first deploy has been done by the admins. Please note that '''everything must be OK on the licensing''' side for a project to be moved ~~out of~~ the ~~studio~~.		** Send an e-mail to studio@boardgamearena.com asking to move the project forward for review. You cannot deploy yourself from the "manage game" page until a first deploy has been done by the admins. Please note that '''everything must be OK on the licensing''' side for a project to be moved to production.
			** When admins publish (push to alpha) they will send an email to the developer with all relevant information about next steps.

Victoria La на 17:36, 11 кастрычніка 2020

2020-10-11T17:36:51Z

← Папярэдн. версія		Версія ад 19:36, 11 кастрычніка 2020
Радок 38:		Радок 38:
	** A prefix for example a trigram for your game that you append to all the css classes to avoid namespace conflicts, i.e. vla_selected vs selected		** A prefix for example a trigram for your game that you append to all the css classes to avoid namespace conflicts, i.e. vla_selected vs selected
	** If you are looking for advice on design and some 3rd party testing you can post a message on the developers forum, and ask other developers, there are a lot of people who will gladly do it.		** If you are looking for advice on design and some 3rd party testing you can post a message on the developers forum, and ask other developers, there are a lot of people who will gladly do it.
	* Finally		* Finally move to Alpha stage
	** If possible (meaning if there is not already a project with that name) copy your project to a new project '''matching exactly the name of the game''' (no prefix or suffix). If not possible move on to the next steps, admin will have to retrieve the other project and overwrite it.		** If possible (meaning if there is not already a project with that name) copy your project to a new project '''matching exactly the name of the game''' (no prefix or suffix). If not possible move on to the next steps, admin will have to retrieve the other project and overwrite it.
	** Create a build for your game from the "manage game" page (using the '''Build a new release version''' section) and check the log to make sure that everything builds fine (after a successful build, you should see a new version in "Versions available for production").		** Create a build for your game from the "manage game" page (using the '''Build a new release version''' section) and check the log to make sure that everything builds fine (after a successful build, you should see a new version in "Versions available for production").
	** Send an e-mail to studio@boardgamearena.com asking to move the project forward for review. You cannot deploy yourself from the "manage game" page until a first deploy has been done by the admins. Please note that '''everything must be OK on the licensing''' side for a project to be moved out of the studio.		** Send an e-mail to studio@boardgamearena.com asking to move the project forward for review. You cannot deploy yourself from the "manage game" page until a first deploy has been done by the admins. Please note that '''everything must be OK on the licensing''' side for a project to be moved out of the studio.

Een: Check translations

2020-09-04T09:32:14Z

Check translations

← Папярэдн. версія		Версія ад 11:32, 4 верасня 2020
Радок 35:		Радок 35:
	** Non-self explanatory graphic elements should have tooltips		** Non-self explanatory graphic elements should have tooltips
	** If graphic elements appear in notification log they should have titles (i.e. title attribute of div) so can be read in non rendered form (i.e. as text only)		** If graphic elements appear in notification log they should have titles (i.e. title attribute of div) so can be read in non rendered form (i.e. as text only)
	** Strings in your source code are ready for translation. See [[Translations]]		** Strings in your source code are ready for translation. See [[Translations]]. You can generate dummy translations for checking that everything is ready for translation from your "Manage game" page.
	** A prefix for example a trigram for your game that you append to all the css classes to avoid namespace conflicts, i.e. vla_selected vs selected		** A prefix for example a trigram for your game that you append to all the css classes to avoid namespace conflicts, i.e. vla_selected vs selected
	** If you are looking for advice on design and some 3rd party testing you can post a message on the developers forum, and ask other developers, there are a lot of people who will gladly do it.		** If you are looking for advice on design and some 3rd party testing you can post a message on the developers forum, and ask other developers, there are a lot of people who will gladly do it.

Een: add background size

2020-08-20T13:10:58Z

add background size

← Папярэдн. версія		Версія ад 15:10, 20 жніўня 2020
Радок 32:		Радок 32:
	** Review BGA UI design Guidelines [[BGA_Studio_Guidelines]]		** Review BGA UI design Guidelines [[BGA_Studio_Guidelines]]
	** If the elements in your game zone don't occupy all the available horizontal space, '''they should be centered'''.		** If the elements in your game zone don't occupy all the available horizontal space, '''they should be centered'''.
			** If your game elements become blurry or pixellated when using the browser zoom, you forgot to use [[Game_art:_img_directory#Use_background-size \| higher resolution images with background-size]]
	** Non-self explanatory graphic elements should have tooltips		** Non-self explanatory graphic elements should have tooltips
	** If graphic elements appear in notification log they should have titles (i.e. title attribute of div) so can be read in non rendered form (i.e. as text only)		** If graphic elements appear in notification log they should have titles (i.e. title attribute of div) so can be read in non rendered form (i.e. as text only)

Een: Indication about successful build

2020-07-10T17:25:58Z

Indication about successful build

← Папярэдн. версія		Версія ад 19:25, 10 ліпеня 2020
Радок 39:		Радок 39:
	* Finally		* Finally
	** If possible (meaning if there is not already a project with that name) copy your project to a new project '''matching exactly the name of the game''' (no prefix or suffix). If not possible move on to the next steps, admin will have to retrieve the other project and overwrite it.		** If possible (meaning if there is not already a project with that name) copy your project to a new project '''matching exactly the name of the game''' (no prefix or suffix). If not possible move on to the next steps, admin will have to retrieve the other project and overwrite it.
	** Create a build for your game from the "manage game" page (using the '''Build a new release version''' section) and check the log to make sure that everything builds fine (~~very often the js~~ build ~~fails because of [[Game_interface_logic:_yourgamename.js#Shrinksafe_minimization \| this constraint]]~~).		** Create a build for your game from the "manage game" page (using the '''Build a new release version''' section) and check the log to make sure that everything builds fine (after a successful build, you should see a new version in "Versions available for production").
	** Send an e-mail to studio@boardgamearena.com asking to move the project forward for review. You cannot deploy yourself from the "manage game" page until a first deploy has been done by the admins. Please note that '''everything must be OK on the licensing''' side for a project to be moved out of the studio.		** Send an e-mail to studio@boardgamearena.com asking to move the project forward for review. You cannot deploy yourself from the "manage game" page until a first deploy has been done by the admins. Please note that '''everything must be OK on the licensing''' side for a project to be moved out of the studio.

Een на 18:15, 6 ліпеня 2020

2020-07-06T18:15:09Z

← Папярэдн. версія		Версія ад 20:15, 6 ліпеня 2020
Радок 20:		Радок 20:
	* Special testing		* Special testing
	** Game is tested with spectator (non player observer): watch you own game with a different account, which is not in the game, and check that it works (and that no secret information is visible). For example, you start a game with express start and your dev0, dev1, dev2 accounts are playing. Then you connect with your dev4 account in a private browser window, and you go to the game.		** Game is tested with spectator (non player observer): watch you own game with a different account, which is not in the game, and check that it works (and that no secret information is visible). For example, you start a game with express start and your dev0, dev1, dev2 accounts are playing. Then you connect with your dev4 account in a private browser window, and you go to the game.
	** Game is tested with in-game replay feature (by clicking on notification log items)		** Game is tested with in-game replay from last move feature (by clicking on notification log items)
	** Game works in Chrome and Firefox browsers at least. Also very recommended to test in IE 11 and Edge.		** Game works in Chrome and Firefox browsers at least. Also very recommended to test in IE 11 and Edge.
	** Game works on mobile device (if you don't have mobile device to test at least test in Chrome with smaller screen, they have a mode for that)		** Game works on mobile device (if you don't have mobile device to test at least test in Chrome with smaller screen, they have a mode for that)

Een: giveExtraTime

2020-06-19T16:13:00Z

giveExtraTime

← Папярэдн. версія		Версія ад 18:13, 19 чэрвеня 2020
Радок 12:		Радок 12:
	** Total size should not exceed 10M, image compression should be used otherwise		** Total size should not exceed 10M, image compression should be used otherwise
	* Server side		* Server side
			** When giving their turn to a player, you give them some extra time with the giveExtraTime() function
	** Game progression is implemented (getGameProgression() in php)		** Game progression is implemented (getGameProgression() in php)
	** Zombie turn is implemented (zombieTurn() in php). Note: it can only be tested if you explicitly click on the quit button to create a zombie. If you are expelled it does not generated a Zombie.		** Zombie turn is implemented (zombieTurn() in php). Note: it can only be tested if you explicitly click on the quit button to create a zombie. If you are expelled it does not generated a Zombie.