Sounds like we have a consensus on that, then: No feeds this release,
unblock the release, and full steam ahead w/o them!.
On 8/28/15 7:37 PM, Till Westmann wrote:
I would agree.
To me the main focus of this release is our ability to release and not
necessarily features (even though it’s certainly nice if we have new working
features ;).
When this release is out, we could immediately work on getting the missing
pieces in and do another release (ideally with another release manager to
spread the knowledge about the process and to smoothen the process).
My 2c,
Till
On Aug 28, 2015, at 10:32 PM, Chen Li <[email protected]> wrote:
Heri was trying to make this part work. Any update from him?
In general, if we cannot make secondary feeds work and documented quickly,
I don't think it's a good idea to include it in this release.
Chen
On Fri, Aug 28, 2015 at 8:03 PM, Ian Maxon <[email protected]> wrote:
What's in master (in the docs) seems to work OK, but that's just
connecting a source to a dataset directly. There's some issue with
printing some tweets (e.g. for $x in dataset Tweets return $x) that
contain special characters, but I'm not sure where that comes from.
However I haven't had much luck getting the secondary feeds/functions
to work. The original documentation seemed to refer to a function that
was renamed/moved, but the renamed function (addHashTags) didn't work
right for me either ( in https://asterix-gerrit.ics.uci.edu/#/c/359/).
If there was a function (that will work reliably) we could use to
create a secondary feed that's already in the code, I think that would
let us include that feature in the docs. Without that though, I don't
know what else can be done besides leaving it hidden for the immediate
future.
- Ian
On Fri, Aug 28, 2015 at 4:56 PM, Michael Carey <[email protected]>
wrote:
Q: So where are things on the feeds front - in terms of what's documented
and what works as advertised (and documented)?
