No, that's it. Just that and making sure that it gets into whatever upgrade script is necessary.
On Thu, Jan 3, 2013 at 4:09 AM, Kishan Kavala <kishan.kav...@citrix.com>wrote: > Marcus, > I can help with schema and related upgrade changes for 686. Are there any > DB changes apart from the unique constraint? > > ~kishan > > -----Original Message----- > From: Marcus Sorensen [mailto:shadow...@gmail.com] > Sent: Thursday, 3 January 2013 11:59 AM > To: cloudstack-dev@incubator.apache.org > Subject: Re: [ACS41] Actions Required: Getting organized for 4.1.0 > > Anyone willing to help me out with 686? This was really a request for > assistance, outlining a simple change with pretty much exactly what I think > needs to be done, but got no response. I'm not sure who really to seek out > for it, which is why I opened the improvement. > On Jan 2, 2013 8:08 AM, "Chip Childers" <chip.child...@sungard.com> wrote: > > > 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 > > >
