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

0.6.0 release #242

Closed
wants to merge 127 commits into from
Closed

0.6.0 release #242

wants to merge 127 commits into from

Conversation

ndelangen
Copy link
Member

@ndelangen ndelangen commented Dec 13, 2016

Checklist:

  • Change code

  • Update documentation

  • Write release notes

  • Migration notes

  • Remove old installation flow (based on nested folders)

  • Regression testing (Robert)

  • Re-test all plugins with latest 0.6.0-dev, and deprecate irrelevant ones

  • Re-check cross-links in docs (Robert)

  • Add deprecation warnings to features that soon would be deleted (Robert)

  • Fix issues Sort by issues #199

  • Re-record an introduction video, showcasing the new installation technique

robhrt7 and others added 15 commits June 18, 2016 15:06
Adding zero-width spaces breaks ejs pattern-finder
# Conflicts:
#	assets/js/modules/loadEvents.js
CHANGE personal grunt-casperjs to global one that has been updated (b…
Ability to launch SourceJS via NodeJS Script
@ndelangen
Copy link
Member Author

@operatino Anything you need we can help with, to make this happen?

…ic-values

BUGFIX: process.env.PORT - Non-numeric values
@robhrt7
Copy link
Member

robhrt7 commented Jan 13, 2017

  • Remove old installation flow (based on nested folders)
  • Regression testing
  • Re-test all plugins with latest 0.6.0-dev, and deprecate irrelevant ones

UPD
moved up to the main list

@ndelangen
Copy link
Member Author

Can you elaborate on what needs to happen for: "Remove old installation flow" ? Can you point to a part of code?

@Alanoll
Copy link

Alanoll commented Jan 13, 2017

If we're almost to a point of release, maybe tag a new nightly? NPM install could then be tested.

@robhrt7
Copy link
Member

robhrt7 commented Jan 16, 2017

Can you elaborate on what needs to happen for: "Remove old installation flow" ? Can you point to a part of code?

Until now there's git clone installation flow, which assumes nested folders structure. We don't want supporting it anymore. But it's hard to tell now which exactly part of the codebase is responsible for that, at least we can clear the mentions form docs.

If we're almost to a point of release, maybe tag a new nightly? NPM install could then be tested.

Yes, we should do it, I'll tag it today.

@ndelangen
Copy link
Member Author

Didn't I already remove that install flow from the documentation?
I'm not so sure there's much code in core dependent on that flow. Might be a lot of plugin need work though...

@robhrt7
Copy link
Member

robhrt7 commented Jan 17, 2017

Released 0.6.0-nightly.7, starting now validating docs and preping final release.

@robhrt7
Copy link
Member

robhrt7 commented Jan 17, 2017

This issue should preferably also be fixed before the release #199

@ndelangen ndelangen closed this Mar 20, 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

Successfully merging this pull request may close these issues.

4 participants