https://bugzilla.wikimedia.org/show_bug.cgi?id=65191
--- Comment #3 from Derk-Jan Hartman <hartman.w...@gmail.com> --- It's not easy, but it's also not totally crazy. You would need a table, keeping track of the beta features, the version of the feature etc. Then check the registrations for the beta features once in a while, see if a new notification needs to be created and scheduled. put the job on the queue and write to the table that you have sent a 'new', 'updated' or another type of notification etc. Ideally we expand echo with some 'action' options, so that users can 'opt-in' to a new feature right from the notification for instance, but that is secondary. Versioning of beta features is important for this one btw. You could have x.y.z x: for generation (the 6 month test period) of an experiment feature (this would send 'new' beta feature motifs) y: significant updates to the experiment (a monthly update, sending feature updated motifs) z: minor changes or revision number or something (small css fix) that don't warrant a notification. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
