Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[UserStory] Automate Java version compatibility with BlueJ product updates #147

Open
5 tasks done
jody opened this issue Nov 23, 2019 · 0 comments
Open
5 tasks done
Labels
epic Epic User Story S: Significant Severity: Significant - in the mainline plan user story User Story

Comments

@jody
Copy link
Collaborator

jody commented Nov 23, 2019

User Story

Essential components

  • Title describes the story
  • Stakeholder type is identified
  • Outcome is described
  • Rationale is explicit
  • Acceptance criteria are verifiable and from the perspective of the stakeholder

Story

As a maintainer
I want the automated build process to update its configuration of Java versions specified for compilation and packaging
so that I don't need to manually update build configuration information (e.g., build.gradle) in response to newer versions of BlueJ

Acceptance Criteria

Scenario 1

Given an updated version of the BlueJ product,
when the updated bluejext.jar file appropriately appears in the QT4BJ repository, and the product build+packaging process is invoked
then the build process completes without error and the resulting product (extension jar file) is compatible with the updated version of BlueJ.

Related Information

See #136

Dependencies

Depends On

(Issues on which this story depends)

Dependents

(Issues dependent on this story)

@jody jody added the user story User Story label Nov 23, 2019
@jody jody added epic Epic User Story low priority labels Nov 26, 2019
@jody jody added S: Significant Severity: Significant - in the mainline plan and removed low priority labels Sep 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Epic User Story S: Significant Severity: Significant - in the mainline plan user story User Story
Projects
None yet
Development

No branches or pull requests

1 participant