Let's make a list of beta blocker issues:
* #2820773: $this->t() should be used instead of t() for Drupal 8 version
* #2817761: Configuration schema is invalid
* #2762353: Drupal 8 Install Instructions
* #2820777: Remove @file tag docblock from all the .php files
* #2719737: No-hotlink: use cache-control header (avoid redirection loops)
* #2751397: Fix coding style to meet Drupal standards
* #2464699: Use write & rename instead of write. Also check content length.
* #2795175: Handle guzzle client exceptions gracefully
* #2819912: Sleep on production, to prevent endless redirection
* #2840952: Hotlink does not redirect to imagestyle path
* #2866908: use_imagecache_root lost
* #2928564: Add stage_file_proxy stream wrapper
Comments
Comment #2
naveenvalechaI reviewed issues and closed one of as duplicate #2767015: PHP files modification as per drupal standards
Comment #3
gregglesComment #4
asrobComment #5
dman commentedThis meta issue is just what I was looking for twhen wondering why we didn't have a stable. Thanks!
FWIW, the existing 8.x-1.0-alpha1 did work for me OOTB, to the point that I needed for a test mirror of a dev site :) . When hotlinking at least.
I'll see if I can spot anything in the list of blockers above that make enough sense to me to test and bump.
(I say commit anything that seems to work for now and tweak edge cases later - better to ask for forgiveness than permission - this is a power-user tool)
Comment #6
geek-merlinAdded imho relevant issues.
Comment #7
jansete commentedHi all, there are some issues for beta1, but there is almost a year between last alpha and dev branch, would it be possible add a new alpha2 release with the latest changes?
Comment #8
geek-merlin> there are some issues for beta1, but there is almost a year between last alpha and dev branch, would it be possible add a new alpha2 release with the latest changes?
@other-maintainers: My gut feeling is to have 2 or 3 alphas before a beta to keep the ball rolling.
I'll take the ball, do some bold commits and roll a new alpha tonite.
Comment #9
geek-merlinComment #10
gregglesIMO it's safer to roll the next stable release and *then* do the bold commits. Wait a month or two and repeat the process.
Releases should follow a period of stability, not a period of high churn.
Comment #11
geek-merlin@greggles: Yes! I'll roll the alpha from yesterdays HEAD.
Comment #12
geek-merlinAdded issue.
Comment #13
geek-merlinI see trees of green and some zombies exorcised. Hope no new demons awoken. Good nite.
Comment #14
geek-merlinComment #15
jansete commentedHi!
When will it be the next alpha release? It would be nice for get this issue (https://www.drupal.org/node/2867108) and works with webprofiler.
Greetings!
Comment #16
gregglesUsing drush release notes project, here are the release notes I see:
~/c/stage_file_proxy (8.x-1.x=) drush rn 8.x-1.0-alpha2 8.x-1.x
Changes since 8.x-1.0-alpha2:
I agree that's a lot! Seems like a good time for a new release. I don't see many new bugs in the issue tracker (maybe none?).
Comment #17
gregglesAlrighty, here's an alpha 3 https://www.drupal.org/project/stage_file_proxy/releases/8.x-1.0-alpha3
Comment #18
NormySan commentedLooks like all the issues are resolved, what's stopping the module from going into a beta release?
I might be able to fix some issues if there are any left blocking a beta release.
Comment #19
jeroentAs @NormySan said. It seems all beta blockers are resolved. Is there still some work left or can we make a beta release?
Comment #20
geek-merlinImho we need #2928564: Add stage_file_proxy stream wrapper here.
Comment #21
BarisW commentedWe already have a beta release, so let's close this one
Comment #22
gregglesIf it happened then I think this is fixed :)