The following are plans for the next couple of weeks:
Improve error messages for the JujuMetadata and other linters (related issue)
Investigate current situation with logs retrieval and errors propagation in nested situations (charmcraft run inside the container, and the charm builder subprocess itsef) (related issue)
Start working on a specification for machine readable output for all Charmcraft commands
Enhance the revisions and other commands’ outputs to show detailed timestamps (related issue)
Fix the user interaction in the --shell option for the pack command (related issue)
We decided to have tracks for the MAJOR.MINOR version numbers too. So I just released Charmcraft to the track 1.5, to where you can subscribe if you don’t want to get out from 1.5.x versions.
I know you’re busy @facundo, so if I should report an issue with charmhub or charmcraft somewhere else please just let me know… but I have noticed a discrepancy in my juju charms ability to run actions… depending on if I upload it directly to AWS… or if I attempt to load via the charmhub… the latter basically not working.
Hello! For what I understand is correct to ask about this issue in the other post. As far as I understand Charmcraft is totally unrelated to this behaviour.
Thanks Teodora for the reminder. We need to decided if it’s worth to have that roadmap now that the team is organized around short term sprints. I got this.
