-
Notifications
You must be signed in to change notification settings - Fork 1
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
Extract unittest from core #293
Labels
Milestone
Comments
thekid
added a commit
to xp-framework/core
that referenced
this issue
Aug 6, 2015
Part of step 1 for xp-framework/rfc#293
thekid
added a commit
to xp-framework/webtest
that referenced
this issue
Aug 6, 2015
thekid
added a commit
to xp-framework/core
that referenced
this issue
Aug 22, 2015
This was referenced Dec 8, 2015
Closed
thekid
added a commit
to xp-framework/core
that referenced
this issue
Jan 21, 2016
* xp-framework/rfc#303: THIS! IS! VERSIOOOOON * xp-framework/rfc#307: Extract XPCLI from core * xp-framework/rfc#301: Extract logging from core * xp-framework/rfc#293: Extract unittest from core * xp-framework/rfc#296: Further minimize the framework * xp-framework/rfc#297: Rebase
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Scope of Change
The
unittest
package will be removed fromxp-framework/core
and split intoxp-framework/unittest
.Rationale
Separate development cycle.
Functionality
The implementation will be done in multiple steps:
Step 1: Extract
First, the libraries will be extracted to their own repositories:
These libraries will be created as overlays for xp-framework/core. This means if they are required, they will have precedence over the classes provided by
core
. This way, libraries can opt in and start using these libraries instead of depending on the version bundled in core (and by doing so, also benefit from any new features they provide). At the same time, the functionality in core will be frozen, meaning no new features will be added.The library version numbers will match that of the last core release their code was still completely equal to: 6.4.2.
Step 2: Transition
The transition period lasts until 7.0.0. Libraries or projects using a dependency constraint of the form
~6.x
or^6.x
will not break; only those using the rather riskydev-master
or>=6.x
variants.Libraries are strongly encouraged to add a dependency on the respective libraries during this time, but are not required to do this.
Step 3: Remove
The code will be removed from xp-framework/core when 7.0.0 is released. So that
core
doesn't depend onunittest
(which depends oncore
), thecore
repository's tests will be run with a bundled distribution.Security considerations
n/a
Speed impact
Dependencies
Related documents
The text was updated successfully, but these errors were encountered: