Change Details

A/C: [] Determine a realistic process to generate release notes [] Determine a way to distribute release notes (e.g. in the tarball? or beside it?) The software in scope for this ticket is: - Wikibase as an extension - WDQS - WDQS UI Possible brainstormed solutions are: - parse git log (maybe with special keywords) - file maintained in the code repo - parse either with dates in the files - or looking through git history - file maintained in the "release" repo - make it part of the phabricator task cycle and somehow extract from there - e.g. maybe a column on the camp board - maybe the navigators should be writing this?

A/C: [] Determine a realistic process to generate release notes [] Determine a way to distribute release notes (e.g. in the tarball? or beside it?) [] document it in an ADR The software in scope for this ticket is: - Wikibase as an extension - WDQS - WDQS UI Possible brainstormed solutions are: - parse git log (maybe with special keywords) - file maintained in the code repo - parse either with dates in the files - or looking through git history - file maintained in the "release" repo - make it part of the phabricator task cycle and somehow extract from there - e.g. maybe a column on the camp board - maybe the navigators should be writing this?

A/C: [] Determine a realistic process to generate release notes [] Determine a way to distribute release notes (e.g. in the tarball? or beside it?) [] document it in an ADR The software in scope for this ticket is: - Wikibase as an extension - WDQS - WDQS UI Possible brainstormed solutions are: - parse git log (maybe with special keywords) - file maintained in the code repo - parse either with dates in the files - or looking through git history - file maintained in the "release" repo - make it part of the phabricator task cycle and somehow extract from there - e.g. maybe a column on the camp board - maybe the navigators should be writing this?