On Mon, 10 Nov 2008 10:42:04 -0500, "Benjamin Reed" <[EMAIL PROTECTED]>
said:
> DJ Gregor wrote:
> > What do you think?
>
> +1 with the caveat that it should be for 1.8, sounds a bit too invasive
> for a 1.6 point release.
I was hoping to get this in sooner so it could meet Tarus' client need
for simplifying notification configuration (see the "Code Help" thread
on the OGP list starting at 2008-10-21). I missed my chance, as I see
that it was committed today (revision 11208, bug #2891). :-(
Tarus, if I could implement the changes that I suggest, could I back-out
the eventd/notification changes you made today? Would you like to see
this in 1.6.x (if so, what's your timeframe?), or should it wait for
1.8?
> On that note, we're looking at attempting to get a 1.6.1 release out
> soon-ish, there are a couple of reasonably important bugfixes.
>
> Should we also look at getting a trunk 1.7.0 unstable release out, just
> so people can start evaluating some of the RESTful stuff, etc.?
+1, if others think we have enough exposed new features for users to be
able to kick the tires. I don't know what's different between
1.6-testing and trunk right now.
- djg
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-devel mailing list
To *unsubscribe* or change your subscription options, see the bottom of this
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel
