On 8/13/13 6:55 PM, Ricardo Berlasso wrote:
2013/8/13 Fernando Cassia fcas...@gmail.com
On Tue, Aug 13, 2013 at 12:24 PM, Jürgen Schmidt jogischm...@gmail.com
wrote:
But if
we change it it annoys potentially other users. The question is what
would be the correct and most often wanted
Hi,
first if all I volunteer to act as the release manager for AOO 4.0.1 if
that is wanted but I am also open to let somebody else to the job ;-)
In preparation for an AOO 4.0.1 release I have first created a AOO400
tag based on revision 1503704. I have also created a new branch AOO401
based
related to 4.0.0, and you already have the build environment set up,
etc.
In preparation for an AOO 4.0.1 release I have first created a AOO400
tag based on revision 1503704. I have also created a new branch AOO401
based on branch AOO400 based on the head revision of the branch.
I noticed
;-)
It is probably best if you continue, since 4.0.1 is very closely
related to 4.0.0, and you already have the build environment set up,
etc.
+1
In preparation for an AOO 4.0.1 release I have first created a AOO400
tag based on revision 1503704. I have also created a new branch AOO401
based
somebody else to the job ;-)
It is probably best if you continue, since 4.0.1 is very closely
related to 4.0.0, and you already have the build environment set up,
etc.
+1
In preparation for an AOO 4.0.1 release I have first created a AOO400
tag based on revision 1503704. I have also created
Hi,
I noticed that Yuri checked in some code on the branch already. Can we
please follow some guideline how we handle such release branches?
Changes on a release branch should be discussed before and should be in
relation to a proposed and approved fix (if you want showstopper) that
will
On Tue, Aug 13, 2013 at 5:24 AM, Jürgen Schmidt jogischm...@gmail.com wrote:
In preparation for an AOO 4.0.1 release I have first created a AOO400
tag based on revision 1503704. I have also created a new branch AOO401
based on branch AOO400 based on the head revision of the branch.
I noticed
if
that is wanted but I am also open to let somebody else to the job ;-)
It is probably best if you continue, since 4.0.1 is very closely
related to 4.0.0, and you already have the build environment set up,
etc.
+1
In preparation for an AOO 4.0.1 release I have first created a AOO400
On 8/13/13 5:55 PM, Yuri Dario wrote:
Hi,
I noticed that Yuri checked in some code on the branch already. Can we
please follow some guideline how we handle such release branches?
Changes on a release branch should be discussed before and should be in
relation to a proposed and
On 8/13/13 6:01 PM, Fernando Cassia wrote:
On Tue, Aug 13, 2013 at 5:24 AM, Jürgen Schmidt jogischm...@gmail.com wrote:
In preparation for an AOO 4.0.1 release I have first created a AOO400
tag based on revision 1503704. I have also created a new branch AOO401
based on branch AOO400 based
On Tue, 13 Aug 2013 12:43:47 -0400
Fernando Cassia fcas...@gmail.com wrote:
On Tue, Aug 13, 2013 at 12:24 PM, Jürgen Schmidt jogischm...@gmail.com
wrote:
But if
we change it it annoys potentially other users. The question is what
would be the correct and most often wanted default.
2013/8/13 Fernando Cassia fcas...@gmail.com
On Tue, Aug 13, 2013 at 12:24 PM, Jürgen Schmidt jogischm...@gmail.com
wrote:
But if
we change it it annoys potentially other users. The question is what
would be the correct and most often wanted default.
What is the purpose of showing
if
that is wanted but I am also open to let somebody else to the job ;-)
It is probably best if you continue, since 4.0.1 is very closely
related to 4.0.0, and you already have the build environment set up,
etc.
+1
In preparation for an AOO 4.0.1 release I have first created a AOO400
tag
for an AOO 4.0.1 release I have first created a AOO400
tag based on revision 1503704. I have also created a new branch AOO401
based on branch AOO400 based on the head revision of the branch.
I noticed that Yuri checked in some code on the branch already. Can we
please follow some guideline how we handle
environment set up,
etc.
+1
I'm fine with another round.
In preparation for an AOO 4.0.1 release I have first created a AOO400
tag based on revision 1503704. I have also created a new branch AOO401
based on branch AOO400 based on the head revision of the branch.
I noticed that Yuri
15 matches
Mail list logo