search

scenarioo / scenarioo-js

Scenarioo writer library to produce feature rich e2e test reports, e.g. from Protractor/WebDriverJS tests with Jasmine
http://www.scenarioo.org
MIT License
10 stars 3 forks source link

ScenariooJS Release 3.0 #21

Closed bruderol closed 8 years ago

bruderol commented 8 years ago

Release 3.0 Preparations:

[x] Release Notes prepared [x] Docu and Migration Guide prepared [x] Changelog prepared [x] checked for remaining TODOs - didnt find any [x] prepare version

xeronimus commented 8 years ago

update: as discussed, if the left-over todos are done, this is ready to be merged into master and released..

bruderol commented 8 years ago

I merged everything between develop and release branch.

Currently release prepration should be done on release-2.2 branch and then merged to develop (and finally to master).

Thank you @xeronimus for helping us.

I will try to get the remaining TODOs fixed as soon as possible.

I see one last problem: I had a look at the generated API docu and it seems to me, that this is not realy understandable, as it seems to me. Te most important things are missing, e.g. I did not find the documentation for the global scenarioo object. We should have a look at this.

bruderol commented 8 years ago

except for the docu, the current state on the release-2.2 branch should be in a good state to be ready to be released.

Although there is still room for improvement concerning screen annotations and other step data.

But I think we could release the current state and then improve on the other remaining issues in version 3.0

bruderol commented 8 years ago

@adiherzog @dola I decided: We will release it as "3.0" - just to be up to date together with our other forthcoming release. We will release this kind of together more or less. I hope you can agree?

adiherzog commented 8 years ago

@bruderol Yes, that's fine.

bruderol commented 8 years ago

Release of ScenariooJS is prepared, will test it a little bit and then release it.

@adiherzog @mi-we @dola I will keep the inofficial "release-2.2"-branch - which not includes some of my latest changes (e.g. typings). For using the very new features (like typings) and testing the release you have to use currently "release-3.0"-branch, if you allready want the newest version, didnt want to accidentaly break any project using the old release candidate branch.

bruderol commented 8 years ago

@adiherzog @mi-we @dola I did it. 3.0.0 now officially released. You can start to use it in your projects from npm (no need to use the release branch url anymore).