Heya Chip, For completeness I've created tickets for some of my stuff.
Planned for release 4.1.0: CLOUDSTACK-726 - Implement L3 Router functionality in Nicira Nvp Plugin (Done) CLOUDSTACK-727 - Add support for Nicira NVP to KVM hypervisor orchestration (In Progress) CLOUDSTACK-729 - Provide RPM spec file without depending on waf and system packages (In Progress) Optional: CLOUDSTACK-728 - Add support for Nicira NVP to VmWare hypervisor orchestration > -----Original Message----- > From: Chip Childers [mailto:chip.child...@sungard.com] > Sent: Wednesday, January 02, 2013 4:08 PM > To: cloudstack-dev@incubator.apache.org > Subject: [ACS41] Actions Required: Getting organized for 4.1.0 > > Hi all, > > As discussed previously [1], we're going to start locking down the list of new > features and improvements that are going to make it into the 4.1.0 release. > Our schedule has us wrapping up all new feature / improvement > development at the end of January, and obviously we need to get organized > around testing the release branch! > > Please take a moment to read through the email below, and take the > appropriate actions where needed. > > tl;dr version: features and improvements need an assignee, the jira ticket > status value is important to update, and feature development that isn't in > the 4.1.0 jira list as of Friday won't be considered for the release. > > -chip > > ******************************* > Unassigned Features / Improvements > ******************************* > > As of right now, there are 6 improvements and 1 new feature that remain > unassigned. The list is below (including the reporter). On Friday, I'll be > removing the 4.1.0 fix version (and setting it to > "Future") for any unassigned new features or improvements currently > tagged for 4.1.0. > > ** Action Requested: if you are actively working on one or more of the items > below, please assign the jira ticket to yourself. > > Improvements: > CLOUDSTACK-67 Resizing XxYton > CLOUDSTACK-24 Multiples IP's on Private LAN with Nat 1:1 Facundo Guerrero > CLOUDSTACK-25 Allow Virtual Load Balancer with basic zone Caleb Call > CLOUDSTACK-686 Allow for same vlan on different physical nics Marcus > Sorensen > CLOUDSTACK-427 Change hardcoded step number references to dynamic > links Jessica Tomechak > CLOUDSTACK-455 Many files listed twice in the spec file David Nalley Major > > New Feature: > CLOUDSTACK-619 CloudStack Marketplace Jie Feng Major > > ******************************* > Status Values > ******************************* > > Looking at the new features and improvements for 4.1.0, I see that we have > the following: > > New Features: > 22 Open / Reopened > 5 Resolved > > Improvements: > 17 Open > 7 Resolved > > What I can't tell is if someone is actually working on the feature (without > digging through comments and commit logs). As of right now, I'm going to > assume that we just aren't keeping the Jira data clean. > However, as we get closer to the end of the month, I'm going to start being > more agressive about looking for status on the work. If nothing is reported, > then we'll have to pull the feature from the 4.1.0 release. > > ** Action Requested: if you are working on new features or improvements > for 4.1.0, can you please be sure to keep the status field (via the workflow > buttons) up to date? > > ******************************* > Improvements and Feature Development not in Jira > ******************************* > > This one is simple. If you are working on something that you expect to > merge into master by the end of the month (anticipating it being part of > 4.1.0), and you don't see it in one of the two jira tables on the release page > [2], then that needs to get fixed. > > ** Action Requested: Ensure that new features / improvements in progress > for 4.1.0 are in Jira! > > > > [1] http://markmail.org/message/lutikbbdn35qe2fe > [2] > https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.1+ > Release
