The only thing I would really like to get rid of is the Jelly templates, with the idea to provide an automatic upgrade from Jelly to Groovy. Other than that it would probably just be breaking email-ext into a "minimal" core plugin with additional features in a more advanced plugin.
On Tue, Feb 18, 2014 at 11:14 AM, Daniel Beck <m...@beckweb.net> wrote: > > On 14.02.2014, at 20:38, Slide <slide.o....@gmail.com> wrote: > > > I'm interested to get some feedback on whether I should continue > spending my time on Extended Email (email-ext), or if there is real > interest in having a new emailing plugin that would be bundled with core > that provided more features than Mailer, but perhaps less out of the box > than email-ext. > > It really depends on the feature set of "New Mailer". While email-ext has > a sometimes overwhelming number of options, most of them are really useful > to users who want full control over the emails Jenkins sends out. Maybe > turn it around, which features would the "New Mailer" you'd like to build > be missing compared to email-ext? > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- Website: http://earl-of-code.com -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
