Sebb,
So to sum up, do we still have blocking issues left? If needed I can brew an
other rc to fix a few more of those minor issues (they are fixed
in trunk).
Thanks,
Francis
On Wed, Sep 2, 2009 at 1:22 AM, Francis De
Brabanderefranci...@gmail.com wrote:
ok, my bad, you can just define the tag
On 02/09/2009, Francis De Brabandere franci...@gmail.com wrote:
Sebb,
So to sum up, do we still have blocking issues left? If needed I can brew an
other rc to fix a few more of those minor issues (they are fixed
in trunk).
IMO the NOTICE file problems need to be fixed.
Thanks,
On 31/08/2009, Francis De Brabandere franci...@gmail.com wrote:
Hi,
The Empire-db community has completed working on Release 2.0.5 and is
now looking for approval of the IPMC to publish the release.
So far the release has been approved by Empire-db committers, but due
to vacation time
[inline reply]
On Tue, Sep 1, 2009 at 5:14 PM, sebbseb...@gmail.com wrote:
The new release candidate uses exactly the same name for the artifacts
and the SVN tag.
This makes it very difficult to determine later what was actually voted on.
Hmm, I don't see how this can be changed when using
On 01/09/2009, Francis De Brabandere franci...@gmail.com wrote:
[inline reply]
On Tue, Sep 1, 2009 at 5:14 PM, sebbseb...@gmail.com wrote:
The new release candidate uses exactly the same name for the artifacts
and the SVN tag.
This makes it very difficult to determine later what
Francis I think we can delete that old directory tree in the trunk.
Rainer
Francis De Brabandere wrote:
Re: [VOTE] Release Empire-db version 2.0.5-incubating (take 2)
[inline reply]
On Tue, Sep 1, 2009 at 5:14 PM, sebbseb...@gmail.com wrote:
The new release candidate uses exactly
On 31/08/2009, Francis De Brabandere franci...@gmail.com wrote:
Hi,
The Empire-db community has completed working on Release 2.0.5 and is
now looking for approval of the IPMC to publish the release.
So far the release has been approved by Empire-db committers, but due
to vacation time
Also, just noticed that there is another version of the tutorial in
Word format (tutorial.doc).
This is stored in SVN alongside tutorial.pdf, but for some reason in
the archive the doc file is stored in one of the subdirectories, viz:
src/empire-db-examples. Not sure why one would need the
On 01/09/2009, Francis De Brabandere franci...@gmail.com wrote:
Also, just noticed that there is another version of the tutorial in
Word format (tutorial.doc).
This is stored in SVN alongside tutorial.pdf, but for some reason in
the archive the doc file is stored in one of the
Sebb,
So to sum up, do we still have blocking issues left? I can brew an
other release to fix a few more of those minor issues (they are fixed
in trunk) but I don't know how to do it with a different tag/version.
Francis
On Tue, Sep 1, 2009 at 7:00 PM, sebbseb...@gmail.com wrote:
On
On Tue, Sep 1, 2009 at 5:46 PM, sebbseb...@gmail.com wrote:
The new release candidate uses exactly the same name for the artifacts
and the SVN tag.
This makes it very difficult to determine later what was actually voted
on.
Hmm, I don't see how this can be changed when using
ok, my bad, you can just define the tag when performing the release
using maven, it does not have to be the same as the version. So you
can set the version to 2.0.5-incubating and the tag to
2.0.5-incubating-rc1. So when the release proceeds we can just copy
over that last rc to the final ant
Hi,
The Empire-db community has completed working on Release 2.0.5 and is
now looking for approval of the IPMC to publish the release.
So far the release has been approved by Empire-db committers, but due
to vacation time and other circumstances the Mentors are unable to
review the release. Hence
13 matches
Mail list logo
