On 08/02/2013 11:22 AM, Dave Cahill wrote:
Now that we've bumped the version number, do we need to
create Upgrade420to430 and add it
to engine/schema/src/com/cloud/upgrade/DatabaseUpgradeChecker.java ?
Yes, I forgot that. I created the SQL file, but I didn't create the Java
files.
Wido
I ran "mvn -P developer -pl developer,tools/devcloud -Ddeploydb" (from [1])
on a fresh checkout of master and got:
[ERROR] Failed to execute goal
org.codehaus.mojo:exec-maven-plugin:1.2.1:java (create-schema) on project
cloud-developer: An exception occured while executing the Java class. null:
InvocationTargetException: The end upgrade version is actually at 4.2.0 but
our management server code version is at 4.3.0-SNAPSHOT -> [Help 1]
Thanks,
Dave.
[1] http://cloudstack.apache.org/develop/environment.html
On Fri, Aug 2, 2013 at 2:37 PM, Radhika Puthiyetath <
radhika.puthiyet...@citrix.com> wrote:
Hi,
I shall give you the complete picture on my doc tasks by EOD today.
You will get a quick update on my doc progress at
https://issues.apache.org/jira/issues/?filter=-1&jql=project%20%3D%20CLOUDSTACK%20AND%20fixVersion%20%3D%20%224.2.0%22%20AND%20assignee%20in%20(currentUser())%20ORDER%20BY%20updatedDate%20DESC
You can start localizing the following:
GSLB (CLOUDSTACK-653)
Document Dedicated Resources: Public IP Addresses and VLANs per Tenant
(CLOUDSTACK-704)
Document limiting resources to domain/accounts (Dedicated Resources)
(CLOUDSTACK-713)
Document user provided hostname to be specified in vCenter instead of
CloudStack generated name (CLOUDSTACK-778)
Documentation for nTier Apps 2.0 : Internal LB (CLOUDSTACK-770)
Document Multiple IP Address per NIC (CLOUDSTACK-24)
Document new default password encoding mechanism, SHA256Salt
(CLOUDSTACK-1734)
Document isolation in advanced zones using PVLAN (CLOUDSTACK-1456)
Document ability to delete events and alerts (CLOUDSTACK-874)
Document the ability to use multiple IP ranges (CLOUDSTACK-702)
Document ability to use only a portion of the network (CLOUDSTACK-705)
Documentation for the add/remove networks (CLOUDSTACK-645)
Doc- Support Multiple Subnets per VLAN (CLOUDSTACK-788)
Document the ability to use multiple IP ranges (CLOUDSTACK-702)
Regards
-Radhika
-----Original Message-----
From: Go Chiba [mailto:go.ch...@gmail.com]
Sent: Thursday, August 01, 2013 2:54 PM
To: dev@cloudstack.apache.org
Subject: Re: [ACS42] Release Status Update: After Code Freeze Next Steps
Thanks Animesh, I'll be checking open tasks too.
On Thu, Aug 1, 2013 at 2:49 AM, Animesh Chaturvedi <
animesh.chaturv...@citrix.com> wrote:
-----Original Message-----
From: Chip Childers [mailto:chip.child...@sungard.com]
Sent: Wednesday, July 31, 2013 8:44 AM
To: dev@cloudstack.apache.org
Subject: Re: [ACS42] Release Status Update: After Code Freeze Next
Steps
On Thu, Aug 01, 2013 at 12:41:16AM +0900, Go Chiba wrote:
Does it already fixed all 4.2 docs?
If yes, I'd like to update it to transifex to go ahead doc
globalization...
I'm not sure.
Animesh? Docs team?
[Animesh>] I am following up with doc team I see a bunch of doc sub
tasks still open.
On Wed, Jul 31, 2013 at 11:20 PM, Chip Childers
<chip.child...@sungard.com>wrote:
On Wed, Jul 31, 2013 at 10:33:51AM +0530, Prasanna Santhanam wrote:
On Tue, Jul 30, 2013 at 10:03:08PM +0000, Animesh Chaturvedi
wrote:
-----Original Message-----
From: Alex Huang [mailto:alex.hu...@citrix.com]
Sent: Tuesday, July 30, 2013 2:06 PM
To: dev@cloudstack.apache.org
Subject: RE: [ACS42] Release Status Update: After Code
Freeze Next
Steps
The best type of commit for keeping things clean is a
cherry-pick.
Merging into the release branch is messy to track as the
RM.
That should be a rule for release branches after code freeze.
--Alex
[Animesh>] Thanks for clarifying, we will follow that for
4.2
Also can we do a git cherry-pick -x? It lists the original
commit from which the cherry was picked. Without it git branch
--contains on a commit id returns the wrong branch the commit
was brought in
from.
Ah... smart idea!
--
千葉 豪 Go Chiba
E-mail:go.ch...@gmail.com
--
千葉 豪 Go Chiba
E-mail:go.ch...@gmail.com
