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

[TECH MGMT] Develop release process(es) for Starter Site, Playbook, and ISLE. #2175

Open
rosiel opened this issue Sep 21, 2022 · 0 comments
Open
Labels
Type: feature request a proposal for a new feature in the software (should be justified by a ‘use case’)

Comments

@rosiel
Copy link
Member

rosiel commented Sep 21, 2022

Overview

We should really be versioning the Playbook, ISLE, and the (new) Islandora Starter Site. Since the first two provide the environment for the third, they form a pretty closely coupled trio.

Can we please use some kind of structured versioning? It would make it much easier in Composer, and could make "what version are you on" something we can talk about.

What kind of user is the feature intended for?

This is a thing we should have for everyone who's using the software. Generally it would help us mature as a software project.

What inspired the request?

The launch of the Starter Site - and accompanying ISLE and Playbook PRs.

The thought "This would be a good place to cut a release" crossed our minds but we don't know of a policy, so we should make one.

What existing behavior do you want changed?

The behaviour of using "dev-" branches of everything. Let's get stable!

Any brand new behavior do you want to add to Islandora?

Yeah you could be on "a stable release" of Islandora (to some degree)

Any related open or closed issues to this feature request?

This covers:

This relates to:

@rosiel rosiel added the Type: feature request a proposal for a new feature in the software (should be justified by a ‘use case’) label Sep 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: feature request a proposal for a new feature in the software (should be justified by a ‘use case’)
Projects
None yet
Development

No branches or pull requests

1 participant