Identify what should be in the next stable release.

Comments

DamienMcKenna created an issue. See original summary.

MustangGB’s picture

MustangGB CreditAttribution: MustangGB commented
Title: Plan for Views 7.x-3.17 release » Plan for Views 7.x-3.18 release
DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented

Thanks MustangGB.

Lets focus on making the next release a bugfix release.

MustangGB’s picture

MustangGB CreditAttribution: MustangGB commented

I 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.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented

@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.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented

Also, 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.

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner as a volunteer and at Chapter Three commented

I 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.

Berdir’s picture

Berdir
Primary language German
Location Switzerland
CreditAttribution: Berdir at MD Systems GmbH commented

Also, 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.

Second that. entityreference tests are for example currently broken because of this.

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner as a volunteer and at Chapter Three commented

So should we release a 3.18, which still basically just has the security fix and then continue with 3.19 after that?

renatog’s picture

renatog
Location Campinas
CreditAttribution: renatog at CI&T commented

Yes.

I agree with @dawehner in #9

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented

I 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.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented
Parent issue: » #2903944: Plan for Views 7.x-3.19 release
MustangGB’s picture

MustangGB CreditAttribution: MustangGB commented

Not sure what the release schedule for this is, but as regressions have been deemed suitable for inclusion I've referenced one.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented

We 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.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented
Status: Active » Fixed

v7.x-3.18 has been released: https://www.drupal.org/project/views/releases/7.x-3.18

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner as a volunteer and at Chapter Three commented

Thank you @DamienMcKenna!

Feliguez’s picture

Feliguez CreditAttribution: Feliguez commented

Hello 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!

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
CreditAttribution: klausi at jobiqo - job board technology commented

You can update straight to the most recent version. If there are new update functions they will all run even if you skipped a release.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.