Am 2018-10-05 um 08:40 schrieb Karl Heinz Marbaise:
Hi,
On 02/10/18 21:56, Michael Osipov wrote:
Am 2018-10-02 um 18:11 schrieb Karl Heinz Marbaise:
> Hi,
>
> Now MNG-6164
>
> will come into play?
>
> What do you think ?
Hopefully, let's push it.
From my point of view of course go on.
Hi,
On 02/10/18 21:56, Michael Osipov wrote:
Am 2018-10-02 um 18:11 schrieb Karl Heinz Marbaise:
> Hi,
>
> Now MNG-6164
>
> will come into play?
>
> What do you think ?
Hopefully, let's push it.
From my point of view of course go on...
Kind regards
Karl Heinz Marbaise
>>>
>>> curre
Am 2018-10-02 um 18:11 schrieb Karl Heinz Marbaise:
> Hi,
>
> Now MNG-6164
>
> will come into play?
>
> What do you think ?
Hopefully, let's push it.
>>>
>>> currently I see only the following open issues:
>>>
>>>
>>> MNG-6412
>>>- currently open @Sylwester can you check this?
>>>
>>> MNG-639
Hi,
Now MNG-6164
will come into play?
What do you think ?
currently I see only the following open issues:
MNG-6412
- currently open @Sylwester can you check this?
MNG-6391
- currently the last Tests are done. Something
which should be changed?
Adding WAGON newest version (3
> Hi,
>
> currently I see only the following open issues:
>
>
> MNG-6412
> - currently open @Sylwester can you check this?
>
> MNG-6391
>- currently the last Tests are done. Something
> which should be changed?
>
> Adding WAGON newest version (3.2.0) to core release?
Yes.
> anythi
Hi,
currently I see only the following open issues:
MNG-6412
- currently open @Sylwester can you check this?
MNG-6391
- currently the last Tests are done. Something
which should be changed?
Adding WAGON newest version (3.2.0) to core release?
anything else which should be part of it?
On Mon, Sep 24, 2018 at 5:49 PM, Hervé BOUTEMY wrote:
>
> most of the release procedure for core is exactly the same as for any
> component:
> https://maven.apache.org/developers/release/maven-core-release.html
Thanks. That's what I was looking for.
--
Elliotte Rusty Harold
elh...@ibiblio.org
Hi Michael,
On 25/09/18 08:07, Michael Osipov wrote:
Am 2018-09-23 um 20:05 schrieb Karl Heinz Marbaise:
Hi,
based on the feedback we had I would like to announce to cut a release
at the end of next Week which means (likely on Saturday/Sunday 29.09 /
30.09 )...
If anyone has something which
Am 2018-09-23 um 20:05 schrieb Karl Heinz Marbaise:
Hi,
based on the feedback we had I would like to announce to cut a release
at the end of next Week which means (likely on Saturday/Sunday 29.09 /
30.09 )...
If anyone has something which should be put into Maven core release the
next week i
notice that the script will have to be updated for sha512 (that is not
published to staging repo)
most of the release procedure for core is exactly the same as for any
component:
https://maven.apache.org/developers/release/maven-core-release.html
Regards,
Hervé
Le lundi 24 septembre 2018, 20:
Hi Elliotte,
On 24/09/18 21:59, Elliotte Rusty Harold wrote:
https://github.com/apache/maven-site
The web site is up-to-date (https://maven.apache.org/ of 09/22/2019
means two days old) ?
Is there something special you have in mind?
Kind regards
Karl Heinz Marbaise
That is, most of the c
https://github.com/apache/maven-site
That is, most of the content found on https://maven.apache.org/
On Mon, Sep 24, 2018 at 2:44 PM, Karl Heinz Marbaise wrote:
> Hi Elliotte,
>
> On 24/09/18 15:42, Elliotte Rusty Harold wrote:
>>
>> What's the procedure/plans for updating the web site and docs
Hi Stephen,
I think we should consider to move the code of that repository into the
ASF...
we need to check the permission with Jason ...
Kind regards
Karl Heinz Marbaise
On 24/09/18 10:39, Stephen Connolly wrote:
I assume you would like my notes from the 3.5.3 release: (also the
source-rele
Hi Stephen,
On 24/09/18 20:43, Karl Heinz Marbaise wrote:
Hi Stephen,
I appreciate that...
That will a lot..
Too fast with the send button.
This should be read as:
That will help a lot...
;-)..
Kind regards
Karl Heinz Marbaise
Thanks.
Kind regards
Karl Heinz Marbaise
On 24/09/18 10:39
Hi Elliotte,
On 24/09/18 15:42, Elliotte Rusty Harold wrote:
What's the procedure/plans for updating the web site and docs in sync
with a new release? Most of the site seems to be in a separate repo.
Can you be more specific about which sites/docs you are talking about?
Kind regards
Karl Hein
Hi Stephen,
I appreciate that...
That will a lot..
Thanks.
Kind regards
Karl Heinz Marbaise
On 24/09/18 10:39, Stephen Connolly wrote:
I assume you would like my notes from the 3.5.3 release: (also the
source-release-validator is at
g...@github.com:stephenc/source-release-validator.git
)
$ e
What's the procedure/plans for updating the web site and docs in sync
with a new release? Most of the site seems to be in a separate repo.
On Sun, Sep 23, 2018 at 2:05 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> based on the feedback we had I would like to announce to cut a release
> at the end of n
I assume you would like my notes from the 3.5.3 release: (also the
source-release-validator is at
g...@github.com:stephenc/source-release-validator.git
)
$ export JAVA_HOME=jdk7
$ export PATH=${JAVA_HOME}/bin:${PATH}
$ export MAVEN_OPTS="-Xmx2048m -XX:MaxPermSize=512m"
$ mvn release:prepare releas
Hi,
On 23/09/18 23:36, Robert Scholte wrote:
Hi,
I'd like to see MNG-6391 fixed. I've noticed on several conferences that
the version in the final line in confusing. This is probably the best
release to fix that.
No problem I will take care to handle this (MNG-6391)
Kind kegards
Karl Heinz
Hi,
I'd like to see MNG-6391 fixed. I've noticed on several conferences that
the version in the final line in confusing. This is probably the best
release to fix that.
MNG-6415 is another easy fix, but is waiting for somebody to create an
integration test to confirm the fix.
thanks,
Rober
Hi,
based on the feedback we had I would like to announce to cut a release
at the end of next Week which means (likely on Saturday/Sunday 29.09 /
30.09 )...
If anyone has something which should be put into Maven core release the
next week is your chance...
So this time I'm stepping up to be
21 matches
Mail list logo
