Closed (fixed)
Project:
Views (for Drupal 7)
Version:
7.x-3.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Plan
Assigned:
Unassigned
Reporter:
Created:
2 Apr 2017 at 18:46 UTC
Updated:
7 Sep 2017 at 07:05 UTC
Jump to comment: Most recent
Comments
Comment #2
mustanggb commentedComment #3
damienmckennaThanks MustangGB.
Lets focus on making the next release a bugfix release.
Comment #4
mustanggb commentedI find such statements disheartening. We already focused on bug fixes for 7.x-3.16 which was 41 (95%) bugs/tasks and 2 (5%) features, of which one of the features was one you started.
I'm already waiting several years for some of the issues I care about to get committed, I'm sure there are many other users in the same boat. I have no time or energy to work on new bug fixes when it's all taken up by constantly re-rolling older patches.
So my counter-proposal would be to focus on what the active userbase cares about, give the guys trying to help you out a little love. With a side-helping of maintainers being a bit more active in the issue queue, there are many issues that we can do nothing further on without maintainer input.
Comment #5
damienmckenna@MustangGB: Please don't take my comment in a negative light. I really do appreciate all of the triage work you've done on the issue queue, it helps tremendously! What would like to do is get a new, small release out in the next few weeks that fixes a few more regressions (like ones I cross-linked today), then we can start at adding some additional features.
Comment #6
damienmckennaAlso, per #2903006-4: Fix tests for 7.x-3.x, other modules are having problems because the current release has broken tests, so getting a small, stable release out ASAP will help everyone.
Comment #7
dawehnerI think ultimately Views is in a maintenance mode state. Also keep in mind that adding features to views in Drupal 7 makes it hard in the future to upgrade to Drupal 8, when views there doesn't have the same features.
Ultimately I'm all about fixing bugs, that's really great, but for features it would be great to get them into Drupal 8 in first, so that kind of problem doesn't exist.
Comment #8
berdirSecond that. entityreference tests are for example currently broken because of this.
Comment #9
dawehnerSo should we release a 3.18, which still basically just has the security fix and then continue with 3.19 after that?
Comment #10
renatog commentedYes.
I agree with @dawehner in #9
Comment #11
damienmckennaI have time tomorrow to get in a few small patches (see referenced issues); I'll be on Slack & IRC tomorrow if anyone wants to chat.
Comment #12
damienmckennaComment #13
mustanggb commentedNot sure what the release schedule for this is, but as regressions have been deemed suitable for inclusion I've referenced one.
Comment #14
damienmckennaWe were planning to do the release today, just to get it out the door. I reviewed that issue and think we should make it a priority to fix in 3.19. Yes, it's a regression, but the bug existed in the last stable release so it isn't a new regression.
Comment #15
damienmckennav7.x-3.18 has been released: https://www.drupal.org/project/views/releases/7.x-3.18
Comment #16
dawehnerThank you @DamienMcKenna!
Comment #17
Feliguez commentedHello guys, I'm using the 7.x-3.16 version and I realised that two consecutive version were launched. My questions is if I need install first the 3.17 and then 3.18 or I just install the latest version. Sorry for my question but is my first production site. Thanks for your help!
Comment #18
klausiYou can update straight to the most recent version. If there are new update functions they will all run even if you skipped a release.