Group D7 has already had quite a few beta releases and is in a very usable state. There is a short list of open tasks that need to go in before we can tag the first full release.

Release blockers

Outstanding

RTBC

Completed

If time permits

Post-release tasks

  • Create Group Demo site(s), document them in a community page, and add link to that page on the project page.

Comments

Pierre.Vriens created an issue. See original summary.

kristiaanvandeneynde’s picture

kristiaanvandeneynde
Primary language Dutch
Location Antwerp, Belgium
CreditAttribution: kristiaanvandeneynde at Deeson commented
Issue summary: View changes
kristiaanvandeneynde’s picture

kristiaanvandeneynde
Primary language Dutch
Location Antwerp, Belgium
CreditAttribution: kristiaanvandeneynde at Deeson commented
Issue summary: View changes
Pierre.Vriens’s picture

Pierre.Vriens CreditAttribution: Pierre.Vriens at In Petto commented
Title: [meta] D7 release roadmap » [meta] 7.x-1.0 release roadmap
Issue summary: View changes
Status: Active » Reviewed & tested by the community

I really think that "adding new feature requests" (which are not bugs) should not be considered as 7.x-1.0 release blockers. I hope that my updated issue description (and title) is acceptable to "soon" get that very-first-ever-official-release-of-group released ...

IMO all that's left now to mark "this" issue as fixed are these steps:

  1. Add the Community documentation link to the Group project page.
  2. Commit the remaining (2) RTBC-issues.
  3. Hit the magic button to create the 7.x-1.0 release.

There are now 595 reported installs of the D7 version of the Group module: 353 of them use beta6, and 47 of them use the dev version ... IMO 353+47=400 sites can't be wrong, this really sounds like way better then a RC-release (and for sure not a beta release anymore) ... also because for the D7 version there are only 2 bugs left in "active" status.

kristiaanvandeneynde’s picture

kristiaanvandeneynde
Primary language Dutch
Location Antwerp, Belgium
CreditAttribution: kristiaanvandeneynde at Deeson commented
Issue summary: View changes
Status: Reviewed & tested by the community » Active

I just spent my entire Saturday reviewing and committing 7.x stuff. We are close, but those patches you moved to 1.1 are all related and need to go into 1.0, especially because one of them may contain an API change.

You're right when you say the low amount of bug reports shows that the module is ready, but I don't want to rush a 1.0 release only to have to release a 1.1 soon thereafter. It would be a shame given the amount of work so many people have put in already.

Again, we are really close. But being patient here will pay off in the long run.

Pierre.Vriens’s picture

Pierre.Vriens CreditAttribution: Pierre.Vriens at In Petto commented
Issue summary: View changes
Pierre.Vriens’s picture

Pierre.Vriens CreditAttribution: Pierre.Vriens at In Petto commented
Issue summary: View changes
Pierre.Vriens’s picture

Pierre.Vriens CreditAttribution: Pierre.Vriens at In Petto commented
Issue summary: View changes
Pierre.Vriens’s picture

Pierre.Vriens CreditAttribution: Pierre.Vriens at In Petto commented
Issue summary: View changes
Pierre.Vriens’s picture

Pierre.Vriens CreditAttribution: Pierre.Vriens at In Petto commented
Issue summary: View changes
Pierre.Vriens’s picture

Pierre.Vriens CreditAttribution: Pierre.Vriens at In Petto commented

The latest D7 release (beta 6) dates from 2015-Aug-27, while there have been 7 alfa and 4 beta releases for D8 in the meantime. Any chance that soon there will be a new D7 release (which include the RTBC issues for D7)?

Also, given the number of reported installs of the D7 version now, it no longer makes sense to just call it a beta release. The D7 version should really be considered at least as "RC"-status. So IMO the next release should either be called RC1, or just 7.x-1.0.

Pierre.Vriens’s picture

Pierre.Vriens CreditAttribution: Pierre.Vriens at In Petto commented
Issue summary: View changes
kristiaanvandeneynde’s picture

kristiaanvandeneynde
Primary language Dutch
Location Antwerp, Belgium
CreditAttribution: kristiaanvandeneynde at Deeson commented

Hey Pierre!

We are getting really close to a first RC for Group 8. I expect a stable Group before the end of Q1 2017. After that, D7 will get the long overdue love it needs to reach a first and final stable release (1.0)

chrisgross’s picture

chrisgross CreditAttribution: chrisgross commented

What is the current status of the D7 release for this module? The latest commit to dev was 6 months ago, with the latest beta release being 2 years old. Is it safe to start using this module and if so, which version (I'm guessing dev + above patches)? Will this cause any problems if and when the next version is released? Organic Groups is way too complicated for most purposes, but this module seems to have been severely neglected.

archimedes’s picture

archimedes CreditAttribution: archimedes commented

Ditto. We've kept an eye on this for a project for awhile, but nothing seems to be moving on D7 side (and there are bigger blocking bugs than those listed in the road map!).

archimedes’s picture

archimedes CreditAttribution: archimedes commented
Issue summary: View changes
kristiaanvandeneynde’s picture

kristiaanvandeneynde
Primary language Dutch
Location Antwerp, Belgium
CreditAttribution: kristiaanvandeneynde at Deeson commented

What is the current status of the D7 release for this module? The latest commit to dev was 6 months ago, with the latest beta release being 2 years old. Is it safe to start using this module and if so, which version (I'm guessing dev + above patches)? Will this cause any problems if and when the next version is released?

Given we're over two years into the D8 cycle and there still isn't a stable D8 release for Group (close, though), I'd say it's only natural that all effort and resources are currently going into the D8 release until that one is out and stable?

but this module seems to have been severely neglected.

I get paid one day a week to work on core and Group. In between my other work I try to follow up on the issue queue to try and prevent it from growing out of proportion. Which it has despite my efforts. On top of that I have a social life and a family to keep happy, as well as a baby on the way. But by all means, tell me I am severely neglecting my open source work.

chrisgross’s picture

chrisgross CreditAttribution: chrisgross commented

@kristiaanvandeneynde We all have personal lives. Valid reasons or not, by definition, it's still neglected. There's no reason to get defensive about it. It's not ridiculous for people to ask questions when a module goes over six months without any changes and has no stable release. In fact I think it's important that we do so, as these questions are also important to the livelihoods of developers all over the world who use Drupal, as unsupported modules (officially or unofficially) cannot be depended on long-term, and doing that research is part of our work.

Soul88’s picture

Soul88
Primary language Ukrainian
Location Ukraine
CreditAttribution: Soul88 commented
Status: Active » Closed (outdated)

We thank everyone for their collaboration on this issue, but as the D7 version is no longer supported, we will now close all D7 issues to keep the issue queue a bit tidier. This information won't go anywhere, it just won't show up on the list of open issues anymore.

Please see: https://www.drupal.org/project/group/issues/3163655 and https://www.drupal.org/project/group/issues/3203863#comment-14100281 for more details.