# Charting / Tree view changes ETA **URL:** \ **Category:** Ignition Early Access\ **Created:** [April 1, 2019, 5:20pm UTC](https://forum.inductiveautomation.com/t/charting-tree-view-changes-eta/23754 "2019-04-01T17:20:03Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Steve\_Laubach](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/steve_laubach/32/60900_2.png) [@Steve\_Laubach](https://forum.inductiveautomation.com/u/Steve_Laubach)\ **Post date:** [April 1, 2019, 5:20pm UTC](https://forum.inductiveautomation.com/t/charting-tree-view-changes-eta/23754/1 "2019-04-01T17:20:03Z")
A while back I asked about upcoming charting changes and learned that charting is in flux currently in Perspective as you evaluate various technologies. > [@Should I expect changes to XY Chart soon?](http://forum.inductiveautomation.com/t/should-i-expect-changes-to-xy-chart-soon/23336): > > I am working on doing easychart-like functionality for XY Chart which includes being able to dynamically specify which tag historian data to show on the chart. I heard a rumor that an update is coming for that body of functionality. So basically, I’m just asking if I should be expecting changes in the next week or few or if I should be working on building a home-grown solution. I’m also interested in any information I can gain about the expression bindings on the XY Chart. I started digging … Can I get an update on where things stand with this? I have a customer asking me about this and they'd like a rough ETA. We understand that nothing is set in stone. I'm also interested in any coming changes for the tree view. Unless I'm doing something wrong it appears that the tree view only allows single selection. I am trying to set up a tree view as my tag viewer and using that to dynamically select what displays on an XY Chart. That can't be done if I can only select one item on the tree at a time. We understand that neither of these things are in the scope of what's expected with the 8.0 launch. We're just trying to gauge if/when we can expect these things in the future so we set expectations properly. ---
**Author:** ![Steve\_Laubach](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/steve_laubach/32/60900_2.png) [@Steve\_Laubach](https://forum.inductiveautomation.com/u/Steve_Laubach)\ **Post date:** [April 4, 2019, 12:38pm UTC](https://forum.inductiveautomation.com/t/charting-tree-view-changes-eta/23754/2 "2019-04-04T12:38:05Z")
My customer is meeting with a stakeholder today at 2 EST. They were hoping to have an official update on ETA for charting changes. They asked me to ask again here. I’m sure you guys are super busy and I don’t want to be a pest. If you can give a rough idea of when we can expect charting updates it would be helpful to me. Thanks ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [April 4, 2019, 3:22pm UTC](https://forum.inductiveautomation.com/t/charting-tree-view-changes-eta/23754/3 "2019-04-04T15:22:26Z")
Probably not 8.0.1, at this point. We’re going to be working on a much more regular release cycle for 8.0, so minor updates should be out monthly. Taken with a huge grain of salt, that means absolutely no earlier than June, and very possibly later than that. It’s high on our list, but once 8.0.0 is out “in the wild” so to speak, there’s a decent chance we end up with a long list of bugs to fix that may take priority. Oh, perfect - there’s a blog post with more details on the faster release cycle: [https://inductiveautomation.com/blog/all-aboard-the-release-train-first-stop-ignition-8](https://inductiveautomation.com/blog/all-aboard-the-release-train-first-stop-ignition-8) ---
**Author:** ![Steve\_Laubach](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/steve_laubach/32/60900_2.png) [@Steve\_Laubach](https://forum.inductiveautomation.com/u/Steve_Laubach)\ **Post date:** [April 4, 2019, 3:34pm UTC](https://forum.inductiveautomation.com/t/charting-tree-view-changes-eta/23754/4 "2019-04-04T15:34:03Z")
> [@paul-griffith](#): > > Probably not 8.0.1, at this point. We’re going to be working on a much more regular release cycle for 8.0, so minor updates should be out monthly. Taken with a huge grain of salt, that means absolutely no earlier than June, and very possibly later than that. It’s high on our list, but once 8.0.0 is out “in the wild” so to speak, there’s a decent chance we end up with a long list of bugs to fix that may take priority. > > Oh, perfect - there’s a blog post with more details on the faster release cycle: [https://inductiveautomation.com/blog/all-aboard-the-release-train-first-stop-ignition-8](https://inductiveautomation.com/blog/all-aboard-the-release-train-first-stop-ignition-8) Thanks for the update. Makes sense. ---
**Author:** ![silverbacknet](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/silverbacknet/32/7385_2.png) [@silverbacknet](https://forum.inductiveautomation.com/u/silverbacknet)\ **Post date:** [April 5, 2019, 9:33pm UTC](https://forum.inductiveautomation.com/t/charting-tree-view-changes-eta/23754/5 "2019-04-05T21:33:36Z")
Given how quickly 8.0’s been evolving, I hope that there will still be a nightly/semi-nightly version for people who can put up with a bit more instability. The regular cadence of bug fixes and important feature landings was a big part of why we adopted 8.0 as the future, and monthly is a long time for ongoing development to sit on bugs. (Even if that means more in-house testing.) ---
**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\ **Post date:** [April 5, 2019, 10:24pm UTC](https://forum.inductiveautomation.com/t/charting-tree-view-changes-eta/23754/6 "2019-04-05T22:24:11Z")
The plan is to continue nightly releases with the expectation that anyone who elects to take such a build would understand that the build is strictly to be used to verify bug fixes that the user is encountering already, and the build should _never_ be used in a production setting. This would allow users to verify a bug fix meets their requirements and begin working with the new build before adopting the stable release a few weeks later. Unfortunately, even though the cadence will be much more regular and releases will drop more often, it won’t change the fact that we can’t fix everything within one or two releases, and many tickets will still fall in the “yes, it’s broken, but everything else is more important” bucket. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [April 6, 2019, 4:03pm UTC](https://forum.inductiveautomation.com/t/charting-tree-view-changes-eta/23754/7 "2019-04-06T16:03:24Z")
If you haven’t read the blog entry Paul linked above, go do so right now. No speculation required.