[Blueprint servercloud-q-juju-release-process] Juju Formal Release Process
Blueprint changed by Antonio Rosales: Work items changed: Work items: - implement this versioning scheme in go juju: TODO - create spec to allow charms to depend on juju versions: TODO + implement this versioning scheme in go juju: DONE + create spec to allow charms to depend on juju versions: INPROGRESS [jimbaker] implement charm versioning in python: DONE implement charm versioning in go: POSTPONED juju to warn on invalid metadata: POSTPONED -- Juju Formal Release Process https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-release-process -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-release-process] Juju Formal Release Process
Blueprint changed by Clint Byrum: Work items changed: Work items: implement this versioning scheme in go juju: TODO create spec to allow charms to depend on juju versions: TODO [jimbaker] implement charm versioning in python: DONE - implement charm versioning in go: TODO + implement charm versioning in go: POSTPONED juju to warn on invalid metadata: TODO -- Juju Formal Release Process https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-release-process -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-release-process] Juju Formal Release Process
Blueprint changed by Clint Byrum: Work items changed: Work items: implement this versioning scheme in go juju: TODO create spec to allow charms to depend on juju versions: TODO [jimbaker] implement charm versioning in python: DONE implement charm versioning in go: POSTPONED - juju to warn on invalid metadata: TODO + juju to warn on invalid metadata: POSTPONED -- Juju Formal Release Process https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-release-process -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-release-process] Juju Formal Release Process
Blueprint changed by Clint Byrum: Work items changed: Work items: implement this versioning scheme in go juju: TODO create spec to allow charms to depend on juju versions: TODO - implement charm versioning in python: TODO + [jimbaker] implement charm versioning in python: DONE implement charm versioning in go: TODO juju to warn on invalid metadata: TODO -- Juju Formal Release Process https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-release-process -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-release-process] Juju Formal Release Process
Blueprint changed by Antonio Rosales: Approver: Robbie Williamson = Antonio Rosales -- Juju Formal Release Process https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-release-process -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-release-process] Juju Formal Release Process
Blueprint changed by Antonio Rosales: Whiteboard changed: python two more milestones before maint: galapagos we'll try the process above honolulu What are the options for 12.10 release to allow the go and juju ports to coexist v2.0.0 go port use alternatives? use completely separate namespace? (juju and juju-dev) (juju and juju-2.0) Is it time to version the charm api as part of this? specify minimum juju version to work (easier with `juju --version` working) treat changes as SRUs and backport to python version (?) worth keeping patch-level in the version... x.x.x actions implement this versioning scheme in go juju spec to allow charms to depend on juju versions BLOCKED on go port toolchain support for this versioning scheme - not related but [clint-fewbar] charm proof should complain about unknown keys in metadata.yaml juju reject charms with invalid metadata + + User Stories: + Juju ninja is developing new feature X and would like to land the feature without impacting the stability for current Juju users. Furthermore, this ninja would also like more insights into how feature development and Juju stability work is progressing in relation to the current Ubuntu release cycle. + + Assumptions: + n/a + + Test Plan + n/a + + Release Note: + None -- Juju Formal Release Process https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-release-process -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-release-process] Juju Formal Release Process
Blueprint changed by Antonio Rosales: Definition Status: Review = Approved -- Juju Formal Release Process https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-release-process -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-release-process] Juju Formal Release Process
Blueprint changed by Antonio Rosales: Priority: Undefined = High -- Juju Formal Release Process https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-release-process -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-release-process] Juju Formal Release Process
Blueprint changed by Antonio Rosales: Approver: Antonio Rosales = Robbie Williamson -- Juju Formal Release Process https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-release-process -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-release-process] Juju Formal Release Process
Blueprint changed by Clint Byrum: Work items changed: Work items: implement this versioning scheme in go juju: TODO create spec to allow charms to depend on juju versions: TODO + implement charm versioning in python: TODO + implement charm versioning in go: TODO juju to warn on invalid metadata: TODO -- Juju Formal Release Process https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-release-process -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-release-process] Juju Formal Release Process
Blueprint changed by Clint Byrum: Definition Status: Discussion = Review -- Juju Formal Release Process https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-release-process -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-release-process] Juju Formal Release Process
Blueprint changed by Clint Byrum: Whiteboard set to: python two more milestones before maint: galapagos we'll try the process above honolulu What are the options for 12.10 release to allow the go and juju ports to coexist v2.0.0 go port use alternatives? use completely separate namespace? (juju and juju-dev) (juju and juju-2.0) Is it time to version the charm api as part of this? specify minimum juju version to work (easier with `juju --version` working) treat changes as SRUs and backport to python version (?) worth keeping patch-level in the version... x.x.x actions implement this versioning scheme in go juju spec to allow charms to depend on juju versions BLOCKED on go port toolchain support for this versioning scheme not related but [clint-fewbar] charm proof should complain about unknown keys in metadata.yaml juju reject charms with invalid metadata -- Juju Formal Release Process https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-release-process -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-release-process] Juju Formal Release Process
Blueprint changed by Clint Byrum: Work items set to: Work items: implement this versioning scheme in go juju: TODO create spec to allow charms to depend on juju versions: TODO juju to warn on invalid metadata: TODO -- Juju Formal Release Process https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-release-process -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-release-process] Juju Formal Release Process
Blueprint changed by Robbie Williamson: Assignee: (none) = Clint Byrum -- Juju Formal Release Process https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-release-process -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-release-process] Juju Formal Release Process
Blueprint changed by Robbie Williamson: Drafter: (none) = Ubuntu Server Team -- Juju Formal Release Process https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-release-process -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-q-juju-release-process] Juju Formal Release Process
Blueprint changed by Robbie Williamson: Definition Status: New = Discussion -- Juju Formal Release Process https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-release-process -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
