On Mon, Apr 22, 2013 at 03:10:11PM -0600, Marcus Sorensen wrote:
> The DB version is set to 4.1.0 on my dev systems, so I think somehow the
> SNAPSHOT was added to the db version only when we hit 4.1.1.
>
> I think it makes sense to roll back to your 4.1.0 if/when possible, that
> way if we need w
The DB version is set to 4.1.0 on my dev systems, so I think somehow the
SNAPSHOT was added to the db version only when we hit 4.1.1.
I think it makes sense to roll back to your 4.1.0 if/when possible, that
way if we need work on the RC we can without rolling forward and back each
time the vote fa
On Mon, Apr 22, 2013 at 03:01:30PM -0600, Marcus Sorensen wrote:
> So if I understand correctly, when the vote fails it will auto revert so we
> can work on the 4.1 branch again? For the moment it's kind of stuck in
> limbo, but maybe that's how it's meant to be. I suppose we work on the
> branch f
So if I understand correctly, when the vote fails it will auto revert so we
can work on the 4.1 branch again? For the moment it's kind of stuck in
limbo, but maybe that's how it's meant to be. I suppose we work on the
branch from the commit where the RC was cut, and then apply any patches
after the
On Mon, Apr 22, 2013 at 04:55:11PM -0400, David Nalley wrote:
> On Mon, Apr 22, 2013 at 4:50 PM, Marcus Sorensen wrote:
> > Why is the HEAD of 4.1 branch now on 4.1.1? Don't we need a stable 4.1.0
> > completed first, before we break 4.1? I ran into several issues today with
> > this, and then fi
On Mon, Apr 22, 2013 at 02:50:52PM -0600, Marcus Sorensen wrote:
> Why is the HEAD of 4.1 branch now on 4.1.1? Don't we need a stable 4.1.0
> completed first, before we break 4.1? I ran into several issues today with
> this, and then finally now there's not a database upgrade from 4.1.0 to
> 4.1.1
On Mon, Apr 22, 2013 at 4:50 PM, Marcus Sorensen wrote:
> Why is the HEAD of 4.1 branch now on 4.1.1? Don't we need a stable 4.1.0
> completed first, before we break 4.1? I ran into several issues today with
> this, and then finally now there's not a database upgrade from 4.1.0 to
> 4.1.1-SNAPSHO
Why is the HEAD of 4.1 branch now on 4.1.1? Don't we need a stable 4.1.0
completed first, before we break 4.1? I ran into several issues today with
this, and then finally now there's not a database upgrade from 4.1.0 to
4.1.1-SNAPSHOT.
On Mon, Apr 22, 2013 at 6:54 AM, Chip Childers wrote:
> Yup
Yup - The script I used to update versions was incomplete. Fixed and
will attempt the process again now.
Thanks Mice!
On Sun, Apr 21, 2013 at 11:34 PM, Mice Xia wrote:
> chip,
>
> in tools/apidoc/pom.xml
> -
> ../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF/
> +
> ../../client/target
chip,
in tools/apidoc/pom.xml
-
../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF/
+
../../client/target/cloud-client-ui-4.1.1-SNAPSHOT/WEB-INF/
-mice
2013/4/22 Chip Childers
> I was about to release the RC for voting, when I hit an error building
> from the 4.1 branch via the follow
I was about to release the RC for voting, when I hit an error building
from the 4.1 branch via the following command:
mvn -P developer,systemvm clean install
Does anyone know what's going wrong here?
Snipped output below:
[INFO] -
11 matches
Mail list logo
