Blueprint changed by Clint Byrum:
Work items changed:
Work items:
Author and communicate proposed release plan to juju mailing list: DONE
- revisit charm store release policy on juju mailing list: TODO
- (Placeholder) Implement testing plan after discussion: BLOCKED
- (Placeholder) Implement
Blueprint changed by Clint Byrum:
Work items changed:
Work items:
Author and communicate proposed release plan to juju mailing list: DONE
- (Placeholder) Implement testing plan after discussion: TODO
- (Placeholder) Implement release plan after discussion: TODO
+ revisit charm store release
Blueprint changed by Clint Byrum:
Work items changed:
Work items:
- Author and communicate proposed release plan to juju mailing list: TODO
+ Author and communicate proposed release plan to juju mailing list: DONE
(Placeholder) Implement testing plan after discussion: TODO
(Placeholder)
Blueprint changed by Antonio Rosales:
Whiteboard changed:
+ Topics:
+ * When do we advance the charms dev focus to each new release of Ubuntu
+ * Should we auto backport and forward port charms, if so, how?
+
Charm Store Policy
- This is a living policy, we will not try to get it
Blueprint changed by Antonio Rosales:
Definition Status: Drafting = Approved
--
Clarifying Charm Store policy around Ubuntu Releases
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charms-release-policy
--
Ubuntu-server-bugs mailing list
Blueprint changed by Antonio Rosales:
Whiteboard changed:
Charm Store Policy
- This is a living policy, we will not try to get it perfect, so trying to
get it perfect is not useful, we need to be agile and revisit our policies on a
regular basis.
- Charm Store doesn't freeze
- I want
Blueprint changed by Antonio Rosales:
Priority: Undefined = High
--
Clarifying Charm Store policy around Ubuntu Releases
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charms-release-policy
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify
Blueprint changed by Clint Byrum:
Work items set to:
Work items:
Author and communicate proposed release plan to juju mailing list: TODO
(Placeholder) Implement testing plan after discussion: TODO
(Placeholder) Implement release plan after discussion: TODO
(Placeholder) Verify Launchpad can
Blueprint changed by Clint Byrum:
Definition Status: Discussion = Drafting
--
Clarifying Charm Store policy around Ubuntu Releases
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charms-release-policy
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Blueprint changed by Jorge O. Castro:
Whiteboard set to:
Charm Store Policy
- This is a living policy, we will not try to get it perfect, so trying to get
it perfect is not useful, we need to be agile and revisit our policies on a
regular basis.
- Charm Store doesn't freeze
- I want
Blueprint changed by Robbie Williamson:
Assignee: (none) = Clint Byrum
--
Clarifying Charm Store policy around Ubuntu Releases
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charms-release-policy
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Blueprint changed by Robbie Williamson:
Drafter: (none) = Ubuntu Server Team
--
Clarifying Charm Store policy around Ubuntu Releases
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charms-release-policy
--
Ubuntu-server-bugs mailing list
Blueprint changed by Robbie Williamson:
Definition Status: New = Discussion
--
Clarifying Charm Store policy around Ubuntu Releases
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charms-release-policy
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
13 matches
Mail list logo