[Hawkular-dev] On the way to the M1 release ...

[Heiko W.Rupp]

Hi,

for the release, Stefan will do all the Maven-magic. Please make sure he 
has what he needs.

It is important to make sure we do not have -SNAPSHOTS in it.
So try to do a release of your component by *today EOB* latest.

Looking at the hawkular-pom, the last (and biggest reminder) is Metrics
- Peter takes care for Pinger, AvailCreator and e2e test to lift to 
0.3.4
- Rumors say that work on UI to lift to 0.3.4 is too heavy
- We currently run against 0.3.2-SNAPSHOT. The build is from April 22nd 
and
can be identified incl. --> we could tag/branch and release 0.3.2 from 
here, to
use it with M1 and then switch over to 0.3.4 afterwards.

Release version will be 1.0.0-Alpha1

For the UI side we will support URLs and also App Server list, but no 
details (so link needs to
be disabled).

Avail data point computation seem wrong:
https://issues.jboss.org/browse/HAWKULAR-295, a
possible fix is available.




On 2 Jun 2015, at 13:53, Jiri Kremser wrote:

> update:
> HAWKULAR-255 - resolved
> HWKINVENT-45 - resolved (UI deletes the metrics before the resource)

Very good.

>
>
>
> | > Hey,
> | >
> | > I see those things that need (at least) to be done/fixed for the 
> next
> | > Wed release:
> | >
> | > - pinger does not respond to deletions (HAWKULAR-235/-263)
> |    In master now
> |
> | - pinger is hardcoded to send to localhost -> Peter working on it.
> | HAWKULAR-106
> |
> | > - inventory does not delete metrics on resource deletion 
> HWKINVENT-45
> | >  (if INV can not make it, can UI send the delete metrics requests 
> ?)
> | > - duplicate URL addition HAWKULAR-255
> | > - alerts is not multi-tenant yet (PR is sent, but may be too
> | > disruptive
> | > ?) HWKALERTS-40
> | > -- Add url fails across tenants for same url (HAWKULAR-277 
> contains a
> | > possible solution)
> |
> | > -- marking alerts as resolved (needs above PR for the backend)
> |     ==> probably too much work on UI side => add checkboxes for
> | "resolved"
> |
> | > - working pagination
> |    ==> HAWKULAR-247 is meant and now marked as resolved
> |
> | > - working availability charts
> | >
> | > - move everything on non-snapshot releases
> | > - update / write documentation on hawkular.org
> | >
> |
> | > As we will most probably not have full app servers functionality,
> | > we should disable that tab so that users are not confused by it
> | > and re-enable and work on it after the release.
> | > Similar for the embedded agent.
> |
> | We will decide that on monday.
> |
> | >
> | > Can we please concentrate on the above (and what else is needed 
> that
> | > is
> | > not yet on the list) to get
> | > the release out?
> | > _______________________________________________
> | > hawkular-dev mailing list
> | > hawkular-dev at lists.jboss.org
> | > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> | _______________________________________________
> | hawkular-dev mailing list
> | hawkular-dev at lists.jboss.org
> | https://lists.jboss.org/mailman/listinfo/hawkular-dev
> |
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev