Tag a 2.3 release of what's currently in 7.x-2.x

This is what I'm running in production, with a content editing team of over 5 non-technical people.

• WYSIWYG-7.x-2.2+75-dev
• TinyMCE 3.5.11 (in EN)

I've used dev version on production sites 4 years:D

Same here, the wysiwyg module is the only module I have using a git sha since has no stable release for years :S

A new alpha release based on what is in dev would definitely help. ^_^

I have been running dev-version of wysiwyg for years without any problem, altough always with ckeditor 4.x. I briefly checked different production versions of wysiwyg module and latest is SHA: a2445d2638d877416ceacc5f943c91865a6baae2 + ckeditor 4.5.6.

I'll second releasing alpha/beta.

I am using current dev release. I have been using dev for years now. It is stable and necessary as the previous stable was lacking in features.

Releasing it as 2.2.1 (or 2.3) would be appreciated.

I've been using the dev release of a few sites for years too. Considering that the "official" advice to get CKEditor 4 support is to run dev, and that advice is two years old, maybe it's well past time for a stable release.

I have 5 production sites running on a range of -dev versions (2.2+54/63/73/75) and not had any issues with them. They are all running CKEditor ranging from 4.4.3 up to 4.5.6

Not sure if that helps much but thought it worth throwing it in the mix.

IME the dev release is good to go stable. We host multiple sites using 7.x-2.2+73-dev or 7.x-2.2+75-dev with CKEditor, primarily in en.

The code in the current 7.x-2.x branch seems to be stable and we're running it on many production sites at the moment (as seems to be the same for people above).

Could I propose that we tag a 2.3 release of what's currently in dev, and then make the blockers mentioned in #2343445: Stable release of Wysiwyg module, v7.x-2.4 please a blocker for 2.4?

Clarifying the title

Please contribute to #2788879: Offer to co-maintain WYSIWYG; restructuring project engineering and maintenance to help get the next release published.

It's probably worth mentioning that everyone running the dev release (probably everyone) isn't getting security team coverage either :(

@danbohea: There *is* security team coverage for modules with dev releases, so long as the module also has stable releases too; the security team does not cover modules that only have dev (or beta, or alpha) releases.

@AdamPS - that's how I thought the security coverage worked too. Happy to be proved wrong though! Can anyone confirm?

See attached screen grab from project page. If security coverage works in any way other than what @AdamPS suggests then it's jolly confusing and needs clarifying.

You are correct about the security team only making security announcements for official releases.

If you report a security issue always do it on security.drupal.org to be sure. The module maintainer(s) and other relevant users will be invited to participate. I don't know exactly what happens if it turns out no stable release is vulnerable, but I suppose the issue will be migrated to the open queue and dealt with as any other bug.

I am currently at DrupalCon and intend to work towards a release here. I was hoping @fizk would be here so I could help him get up to speed with the project too, but we'll stick to email and IRC for now.

I'm not going to push in many more changes before tagging a release, just what's needed to get the project back on its feet and into a state I can live with. I won't be digging through the queue for anything, but if a new patch is submitted for something and it's small, isolated, and commit ready I'll include it if I can while already "passing by" (like the simple coding style fix for NULLs that went in the other day).
Just don't flood me with all coding style patches just yet or I'll drown. I'll focus on a proper code cleanup for a later release ;)
The patches I'll focus on are the ones making a release, and future maintenance, easier. A cornerstone in that was to finally drop openWYSIWYG. It's been a major headache trying to get it to play nice, so it got the axe just now.
I'm a bit undecided about some of the other editors. I don't think they'll be around for much longer, but so far I can keep them in check (though be it with a few hacks). Dropping support for older versions of some editors is also an option, TinyMCE 2 goes next...

Thanks @TwoD! I'll make myself available as much as possible while you're at DrupalCon via email and IRC if anything comes up. Have a good time!

I am also at Drupalcon and helping @TwoD

I hope I'm not cluttering this thread, but I just wanted to say thank you to TwoD, fizk, and anyone else putting in time on getting this released. I much rather prefer TinyMCE 4 over CKEditor, and I'm really happy to see this module coming back to life.

+1 for a stable release.

And +1 for danbohea's security concerns.

Thanks

Is there any chance of getting a new stable release soon?

I'm seeing a lot of life in the commit log, but still no new stable release in 4 years. We have been using the dev release on live sites for probably some years now.

The latest beta releases of media does not seem to play nice with ckeditor 3.6, so the latest stable is getting less and less usable.

#2832384: media_vimeo and media_wysiwyg tokenhandling broken except when using the dev version of wysiwyg

@fuzzy76 honestly the latest "stable" hasn't been stable for awhile now. I wouldn't recommend it for new development. And given the many years of stagnation here, unfortunately I've moved on to other WYSIWYG options. Some day maybe I'll return, but after many months of offering to help, offering to coordinate funding, offering to find comaintainers, and the module still going without an update, I had to cut my losses and look elsewhere.

+1 for Please tag dev and make a release

Tagged and released.

As you probably noticed, I snuck in a couple of extra patches which I know a lot of you have been waiting for. I did actually promise myself that there would be a release before the year is over, no matter what, but I think the release gets a lot better with them in. All I can do is hope you agree.

Further releases will be more frequent, and thus likely less interesting on their own, but I think you all agree that will be better than having the development cycle drag on this long again.

I created a new Plan issue for 2.4: #2840252: Plan for WYSIWYG 7.x-2.5 release

Thanks, all!