Roadmap of Simplenews 6.x-2.0 / 7.x

Thanks for asking. Here are my thoughts.

6.x-1.x
Security & Critical Bugfixes only. No features.
Many bugs in 1.x are due to architectural limitations whereas the 6.x-2.x rewrite is needed. If you run into such a feature / rewrite related bug, consider upgrading and help us make 6.x-2.x stable NOW.

6.x-2.x
There are just a few critical bugs remaining. Most importantly:
#776370: Unsubscribe link fails for non-administrators
And possibly multilanguage / sending issues like:
#875672: Wrong "Sent" numbers on "Created issues" list
#943980: newsletter send ignores subscriber's language preference
#780132: Mail/Send error leads to infinite loop and cron crash
While there are few blockers, i would love to see some more features (also in issue tracker) implemented. However without contributors completing them i'll drop most feature requests for 6.x-2.x and they won't be implemented ever in 6.x.
I really would love to see some improvements here - namely:
#668730: Integrate simplenews with views module
#221521: SimpleNews Service
(and many more i'd really love to see coming...)
I'll wait for some replies to see if someone takes the ball. If not i'll publish a stable release very soon.
Help us testing NOW and we'll proceed faster!
Latest or as soon as D7 releases we'll release 6.x-2.x and won't wait any further uncompleted feature.

7.x-1.x
Right after 6.x-2.x stable release we'll freeze features for all 6.x series. Before upgrading to 7.x you NEED to upgrade to 6.x-2.x.
We won't guarantee upgrade path from current 7.x and reported upgrade issues will be "won't fix".
First all 6.x-2.x features need to be ported and 7.x needs a lot of testing. Then we'll complete the upgrade path.
Some architectural changes in D7 might lead to improvements and additional rewrites before we release a first stable.
As of today, feel free to submit patches for D7 which implement D6->D7 transition straight forward. I'll commit them immediately to get response.
If you want to push a feature in D7, you need to help us port D6 features first.

NOW: Join the party! :-)

I've added a new paragraph on the project front page already that contains a link to here right after the post. :-) Thx

Thanks for the great work. Would it be possible to start with an 6.x-2 alfa release so people can test more easily?

Yes! I'm all for wrap up of 6.x-2.0, port to 7.x-2.0, then add new features.

Simplenews has alot to offer as-is for 7.0 installations. Not having a 7.x-1.x to 7.x-2.x upgrade path cuts out anyone wanting to make an early 7.0 site with a newsletter using Simplenews. Seems like alot of sites!

Install stats say it's used on 27028 sites. It would be awesome if Simplenews was #D7CX

Mike

MichaelCole
Our first 7.x release will be 7.x-1.x which will be a SUCCESSOR of 6.x-2.x. There won't be any 7.x-1.x > 7.x-2.x or so. (7.x-1.x contains some rewrites and is not directly related to 6.x-1.x.
We won't cut someone out. I simply relate to the habit that it is common that -dev releases don't provide upgrade pathes.

Feel free to make simplenews #D7CX. You can install it, work bugs out, port 6.x-1.x > 6.x-2.x patches (from issue queue) and work on the code.
Alternatively i'm perfectly happy to make #D7CX happen, as soon as someone provides funds for 2..3 Weeks of Work. Will you?

I'm working right now on #221521: SimpleNews Service.
I've already submitted a patch for #948894: Add better email validation support (the feature request linked to #780132: Mail/Send error leads to infinite loop and cron crash).

After I'm done with the service, I plan to try working on the release-blocker (#776370: Unsubscribe link fails for non-administrators).

Best regards,

Hop, #221521: SimpleNews Service needs review ! Please go help by reviewing it allowing miro_dietiker to focus on remaining issues.

+1 for an alpha as well, it will allows translations team to start.

I think Miro's will is to release a 6.x-2.x alpha version where there is no critical issue anymore. We're down to one, according to this. Feel free to help, we're doing as best as we can to release it as soon as possible ;)

:-) Right i would like to have a clear understanding on what we finally deliver (also regarding the UI appearance) before releasing an alpha.

Subscribe.

subscribe

subscribe

subscribe

subscribe

Subscribe

From where I stand, I think the release of the 6.x-2.x version will happen where there is no critical open issue any more (we're not to far away).
Regarding the 7.x-1.x, I think there's still some code to port from the 6.x-2.x version, it's currently usable (at least I think) but there still is the upgrade path from D6 missing. As soon as the upgrade path is completed, a release will happen.

Anybody willing to help fix the remaining bugs or test the D6->D7 upgrade path is welcome !

subscribing

subscribe

Subscribe

We're now closer than ever of a new 6.x-2.0-alpha2 release, please help us go faster by reviewing #1036036: "Published", "Sent" and "Status" columns are empty.

http://drupal.org/node/1129780 : 6.x-2.0-alpha2 is now out, with lots of bugfixes !

Subscribe

Simon!

How to send by simplenews not all node, but only a teaser?!

Still can't find information :((( Please, help!

@arissston, please don't hijack the thread, and create a new issue for your support request.

subscribe

subs

Subscribe. Any prevision on 7.x. alpha release? Thanks!

As stated here:

Regarding the 7.x-1.x, I think there's still some code to port from the 6.x-2.x version, it's currently usable (at least I think) but there still is the upgrade path from D6 missing. As soon as the upgrade path is completed, a release will happen.

D6 version is not even complete yet; better focus on getting D6 perfect first:
* SimpleNews in alpha version;
* SimpleNews Content Selection in dev version;
* SimpleNews Scheduler in beta version.

To my opinion it might be better to first have final D6 versions. Don't hurry, don't worry! Maybe it will also help to have a complete rewrite for D7 after D6 versions have been completed?

(Only D7 core exist yet; it will take a year before most modules are ported, so just keep in line with that - like half a year?)

ClearXS
We're already on that roadmap since half a year and it's fine.
Although the original intention was to release sn D6 half a year ago, there are constantly coming up new critical issues we want to fix before stable release.
With some funds we would immediately complete that work. But there isn't.
We're using the D6.x-2.x version in production since a long time.

However, the D7 port is here and was pushed to make SN7 up-to-date.
We're focussing on that line to make D7 futureproof. There's much more than SN itself we need to care.
We already ported 5+Modules and D7 is the only version to push if you don't want to waste your time as a maintainer. Since months we're only starting new projects with D7.

Feel free to support D6 development. I hope you understand my point of view.

OK, thanks for the explanation!

I'm sorry that I have no PHP experience, while my money+time is in other volunteer projects...

If you are so eager in pushing the D7 version how come it has not seen a single commit since June although there are so many critical errors in the current version? Can you give me an idea to when a beta version for D7 could be available? Mid September? End of Year?

@reptilex : you're welcome to propose patches or to give funds if you want to see the development go faster. There are only 2 critical issues on 7.x-1.-x-dev as far as I can see. If you see others, please take the time to report them, and we'll see what we can do when we have the time.
Alpha version will be available when the upgrade has been tested, as already stated above on this issue. Please test, give some feedback and then we can move on to alpha, and later beta, status.
As every other big module, we need help from the community of Simplenews users to thoroughly test different upgrades (single language / multilangual, a few subscribers, a lot of them, open / closed subscription, and so on). You're welcome to help !

;-) Thank you Simon.

Roadmaps are established, and work is going great on 7.x-1.x. Let's close this issue.

> Roadmaps are established
Very happy to close this issue, but could you update the project page with information about what the roadmap is now?
I'm aware that 6.x-1.x has just gone to not-supported, which is what prompted me to check the project page and this issue.

Thanks Miro and Simon for all the hard work you put in on this.

Andy

6.x-2.x is already used and stable in several production sites. It's now the recommended version for the 6.x branch, because we were getting tired of people creating issues on 6.x-1.x branch that has been unmaintained for more than a year. We're still waiting for people confirming that the upgrade path is working in the 6.x-2.x to indicate that it is stable.
You may expect a little work on the 6.x branch (especially if there still are open bug reports), but the version is quite stable.