Skip to content

v0.6.0 Release Checklist #163

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

Open
5 of 8 tasks
dclear opened this issue Sep 27, 2018 · 12 comments
Open
5 of 8 tasks

v0.6.0 Release Checklist #163

dclear opened this issue Sep 27, 2018 · 12 comments
Assignees

Comments

@dclear
Copy link
Contributor

dclear commented Sep 27, 2018

Remaining actions:

  • Review release (product owner)
  • Approve release (Product Owner, QA Lead, Release manager)
  • Create binaries (any DRUD maintainer)
  • Draft release notes (release manager)
    ~~ [ ] Social media announcement, blog, newsletter, etc~~
  • Create release (release manager)
  • Update Roadmap (TPM/release manager)
  • Verify that autoupdate is working properly
  • Followup issues spun off if we need them.

For additional background information, please see our Product Release instructions here.

@dclear dclear added this to the v0.6.0 milestone Sep 27, 2018
@dclear
Copy link
Contributor Author

dclear commented Dec 5, 2018

Let Monica and I know when you're ready for release testing, @alkymst

@alkymst
Copy link
Contributor

alkymst commented Dec 7, 2018

@dclear dclear assigned unn and rfay Dec 7, 2018
@dclear
Copy link
Contributor Author

dclear commented Dec 7, 2018

ty @alkymst !

@rfay
Copy link
Member

rfay commented Dec 7, 2018

I took it for a quick spin: It seems to work fine with ddev v0.4.1. Some small oddities befitting of an alpha, don't recommend working them too much.

  • The "new" button doesn't work.

ddev-ui

* For sometime in the future, I still can't figure out selecting the correct directory. Tried "connecting existing" and it ended up creating a subdir. * Didn't understand at all what the "clean container" tab might be for. * "Start new project" with Drupal 6 seems like it will seem silly to people. That said, the defaults don't work out right. It defaults to php 7.1, which is incompatible with D6.

Testing with ddev/ddev#1307 (json additions)

  • Tried "connect existing project" and it said "update existing config.yaml", I did, got this:

ddev-ui_and_ddev_ui_0_6_0

* Tried "connect existing project" and got this:

ddev-ui

The most critical need remains the same: Automated tests. It will never be possible to catch regressions in a complex gui without automated tests.

Great news: Each error I encountered was recoverable. I clicked "OK" and got on with my business.

@unn
Copy link
Contributor

unn commented Dec 7, 2018

Is there a changelog I can look over? https://github.com/drud/ddev-ui/milestone/6

@dclear
Copy link
Contributor Author

dclear commented Dec 7, 2018

@alkymst : can you do a pass on the issues on the board at https://github.com/orgs/drud/projects/25 and let us know what's done and included in release for testing? https://github.com/drud/ddev-ui/milestone/6 - thanks!

@unn
Copy link
Contributor

unn commented Dec 7, 2018

This has my approval. Good work.

@dclear dclear removed this from the v0.6.0 milestone Dec 7, 2018
@alkymst
Copy link
Contributor

alkymst commented Dec 7, 2018

Randy,

The new button issue is actually more a design issue than anything. If works, it's taking you to the view to create a new project. The issue is it's the same view you land on, or the default index page. We used to have a datagrid style list on the index, but it didn't make sense to have duplicate project lists. So unless you are looking at a project you are seeing the create project view. If you click on new while looking at a project you will see the button works as expected. Need to think this through in the redesign.

@alkymst
Copy link
Contributor

alkymst commented Dec 7, 2018

Randy,

For sometime in the future, I still can't figure out selecting the correct directory. Tried "connecting existing" and it ended up creating a subdir. * Didn't understand at all what the "clean container" tab might be for. * "Start new project" with Drupal 6 seems like it will seem silly to people. That said, the defaults don't work out right. It defaults to php 7.1, which is incompatible with D6.

I'm going to look into these issues. As for the D6, you might be right on that. as for the PHP configs, I can setup defaults for each that make more sense. I created a yaml file to handle some of this logic vs putting it in code I'll extend the default container settings for each CMS here - https://github.com/drud/ddev-ui/blob/master/src/resources/InstallProfiles.yaml - Good catch!

@alkymst
Copy link
Contributor

alkymst commented Dec 7, 2018

As for testing with ddev/ddev#1307 (json additions) this need to be addressed soon, ideally before your next release then this goes live.

@mafriend
Copy link
Contributor

mafriend commented Dec 7, 2018

Hey folks!

I did some regression testing using a macOS running mojave 10.14.1 and here are my findings!
https://cl.ly/c0e021baf09d
https://cl.ly/539577d211db

A few issues were found and those have been filed in the appropriate projects, but no blockers were uncovered during testing (though @alkymst is working on the fix for the php project installation)! We should be good to go whenever that bug is fixed!

Thanks!

@dclear
Copy link
Contributor Author

dclear commented Dec 7, 2018

ty @mafriend!

@alkymst alkymst removed their assignment Feb 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants