charm store series enablement/timing (unrecognized series "zesty")

Uros Jovanovic uros.jovanovic at canonical.com
Tue Dec 6 16:05:27 UTC 2016


This should be resolved now.

On Sat, Dec 3, 2016 at 5:20 PM, Ryan Beisner <ryan.beisner at canonical.com>
wrote:

> Hi All,
>
> Do we have an eta for zesty series recognition in the charm store?  It
> looks like it is already committed in master, so I imagine it's just a
> matter of the store release schedule.
>
> OpenStack Charm CI consumes cs: artifacts for our charm dev and test, and
> all of the official OpenStack charms are multi-series.  That means that the
> presence of zesty series metadata effectively halts our dev/test and CI for
> all series.  We are seeing:
>
> unrecognized series "zesty" in metadata
> https://github.com/juju/charmstore/issues/695
>
>
> To unblock devs in the mean time, I've raised reviews to remove zesty
> series metadata from the affected charm repos.
>
> I think it's pretty important for the charm store to get ahead of this by
> always enabling the next dev series as soon as that series opens for
> development.  And, we'll look before we leap on each cycle.
>
> Cheers & thanks,
>
> Ryan
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20161206/de054f51/attachment.html>


More information about the Juju-dev mailing list