- π©π°Denmark Birk
I can't find any issue related to this, so I'll ask here.
What are the blockers for creating a new beta/rc?
There are currently 3 versions of ECK: 7.x-2.x, 7.x-3.x, and 8.x-1.x.
This version is dead in drupal.org, but there are lots of nice, but unstable, features in there. There is a copy of this branch on github, and the current plan is to move these features to 2.x: https://github.com/fmizzell/eck
These are the features in 3.x that will need to be backported:
mihai_brb is currently working on porting the UI and UX improvements that we did for properties in 3.x. If anyone is interested in moving some of the other features over, let me know.
The 7.x-2.x branch is pretty stable with rc releases for 2.0.
We will continue development on this branch with new features added, but my plan is to have very short feature release cycles.
The idea will be that we will not merge any new features without a nice set of behat tests. This should give us some confidence on the stability of the features. So as soon as the first new feature is merge, we can tag a 7.x-2.1-beta1 release.
After a month or so, we should be getting a nice set of bug reports related to the new feature, and once those bugs are fixed we can start tagging rc releases.
In a perfect world this will mean that we can have one new feature every month and a half, and keep a pretty stable module at the same time.
The features that we all would like to see during the 2.x cycle are the following ones #1971326: What functionality would you like in 3.x β :
There is an alpha release which can be tested and further development is being done by legolasbo. A non-exhaustive list of planned changes can be found below.
Active
3.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I can't find any issue related to this, so I'll ask here.
What are the blockers for creating a new beta/rc?