Since the SF migration, the mailing list no longer receives emails on changes of commits/Bugs/Feature Requests.
Is there any setting to receive changes to a specific mailing list/email address?
It's strange that this wasn't transferred over during the upgrade, since it should now.
Anyway, this is set via Admin -> Tools, then under each tickets instance, you shuld see a "Options" link. You can define an address to send updates to there.
Let me know if this helps!
Chris Tsai, SourceForge.net Support
Setting "Email ticket notifications to" does not work, it was set on:
Also, there is not place to set the dev-list mailing list to receive commits.
@Chris modifying each ticket individually doesn't make sense.
What about the email commit emails?
Is it possible to switch back to the old "Classic" forge. As far as I can see it was better for our expectations.
@Ahmed it seems that the ticket stays on pending even if you've answer (a new feature probably? :-(). Perhaps can you change the status?
Can not change status :(
Are you getting any notifications on your project right now? We've been investigating a bug where the notifications for a project don't get turned back on after upgrade (we turn it off during the upgrade process so we don't bombard you with emails for each migrated ticket, forum post, etc).
As for commit emails, we have instructions for adding the appropriate hook here: https://sourceforge.net/p/forge/community-docs/Subversion/#adding-an-svnnotify-hook
Marc: that's a per ticket tracker setting, not a setting for individual tickets.
If you want, we can roll you back to the classic system for now. Note however that any changes made on the new tools will be not be carried over with the revert. So, any ticket changes, and code commits made since the upgrade will not apply to the old repo/trackers.
These pages for the new system will still be active if you want to use that as a reference to carry back. But they just won't be linked to anymore from the project summary page (all the links will be for the old tools again).
With that knowledge, let me know how you'd like to proceed.
Hold your horses, Marc.
@Chris: our two basic requirements are: commit emails, and ticket emails, which seems to be available but not working.
For one single commit an email has been sent, but it is not active now.
Someone (not sure about March) has added post-commit:
[asashour@shell-24009 hooks]$ more post-commit-user
# THIS FILE IS AUTOGENERATED - DO NOT EDIT
/var/local/mastertree/host/sfp-svn/hook-scripts/keepsake -p "$1" -r "$2"
/var/local/mastertree/host/sfp-svn/hook-scripts/svnnotify --repos-path "$1" --re
vision "$2" --to "email@example.com" --subject-prefix "SF.n
et SVN: htmlunit:" --subject-cx --no-first-line --with-diff --viewcvs-url "http:
//htmlunit.svn.sourceforge.net/htmlunit/?rev=%s&view=rev" --user-domain "users.s
ourceforge.net" --footer "This was sent by the SourceForge.net collaborative dev
elopment platform, the world's largest Open Source development site." -l /usr/bi
n/svnlook --max-diff-length 100000
Please note /var/local/mastertree/host/sfp-svn/hook-scripts/svnnotify and not "/usr/bin/svnnotify" as hinted in the docs.
Also, Admin->Tools->Bus and Feature Requests are not more available, but "Tickets" is.
Again, enabling "Tickets" and setting "Email ticket Notification to" does not send any emails.
1) okay, so for ticket emails, I think we're asking the wrong question. Are you getting any ticket notifications for your project at all? From your original question, I thought you were simply asking how to send these to a mailing list. Note, we are investigating an issue where the notifications for a project don't get turned back on after migration.
2) for commit emails, please update your hook script to the new path for the new repository setup, since this isn't done automatically yet. We are working on doing this automatically with this ticket: [allura:tickets:#5076]
1) no, we don't get any ticket notifications at all in the mailing list.
2) I've now updated the commit hook as explained, just modifying the user-domain parameter. It now works for me, let's wait what happen for the other committers (the old one was working for my commits but not for the commits of the other committers).
Note that the link to administrate the mailing lists is not working. Accessing it directly (like https://lists.sourceforge.net/lists/admin/htmlunit-develop) seems to work.
While we're looking into the root cause more, we've manually re-enabled notifications for projects that still had them turned off after the upgrade. Your project was on that list.
Let me know if that helped!
emails are now sent for bugs changes. The problem is that they are sent with the author of the bug change as From: field and therefore are automatically discarded by mailman.
Okay great, as for getting your mailing list set up, you can add the following regex to your mailing list configuration under Privacy Options -> Sender Filters, in the "accept_these_nonmembers" option:
Yes, we are now receiving ticket changes as email notification from all users of SF on the mailing list.
You can close this ticket.
Thanks for your help.
Excellent, thanks for the confirmation.
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.