On 24.05.2011 22:19, Mark Thomas wrote:
On 24/05/2011 20:24, Konstantin Kolinko wrote:
2011/5/24 Mark Thomas ma...@apache.org:
1. In what repository will the artifacts go?
IIRC, there is some additional repository. I think it wouldn't be good
to have them in /repos/asf/
There is a separate
On 18/05/2011 17:33, William A. Rowe Jr. wrote:
On 5/18/2011 9:22 AM, Mark Thomas wrote:
On 18/05/2011 15:06, Konstantin Kolinko wrote:
2011/5/18 Mark Thomas ma...@apache.org:
All,
We have the option to move to svnpubsub for managing our releases.
Rather than copying artefacts to people.a.o
2011/5/24 Mark Thomas ma...@apache.org:
1. In what repository will the artifacts go?
IIRC, there is some additional repository. I think it wouldn't be good
to have them in /repos/asf/
There is a separate /dist repo
https://dist.apache.org/repos/dist/... dev and release, with tomcat as a
On 24/05/2011 20:24, Konstantin Kolinko wrote:
2011/5/24 Mark Thomas ma...@apache.org:
1. In what repository will the artifacts go?
IIRC, there is some additional repository. I think it wouldn't be good
to have them in /repos/asf/
There is a separate /dist repo
+1
On Thu, May 19, 2011 at 1:38 AM, Mark Thomas ma...@apache.org wrote:
All,
We have the option to move to svnpubsub for managing our releases.
Rather than copying artefacts to people.a.o and then waiting for rsync
(every around 2 hours) we would commit the artefacts to svn and a commit
All,
We have the option to move to svnpubsub for managing our releases.
Rather than copying artefacts to people.a.o and then waiting for rsync
(every around 2 hours) we would commit the artefacts to svn and a commit
hook would update the /dist/tomcat area on the www servers immediately.
If folks
2011/5/18 Mark Thomas ma...@apache.org:
All,
We have the option to move to svnpubsub for managing our releases.
Rather than copying artefacts to people.a.o and then waiting for rsync
(every around 2 hours) we would commit the artefacts to svn and a commit
hook would update the /dist/tomcat
On 18/05/2011 15:06, Konstantin Kolinko wrote:
2011/5/18 Mark Thomas ma...@apache.org:
All,
We have the option to move to svnpubsub for managing our releases.
Rather than copying artefacts to people.a.o and then waiting for rsync
(every around 2 hours) we would commit the artefacts to svn
+1 sounds good
Filip
On 5/18/2011 7:38 AM, Mark Thomas wrote:
All,
We have the option to move to svnpubsub for managing our releases.
Rather than copying artefacts to people.a.o and then waiting for rsync
(every around 2 hours) we would commit the artefacts to svn and a commit
hook would
2011/5/18 Mark Thomas ma...@apache.org:
1. In what repository will the artifacts go?
IIRC, there is some additional repository. I think it wouldn't be good
to have them in /repos/asf/
There is a separate /dist repo
2. You will have to upload Javadocs.
Huh? We are talking about
+1
On Wed, May 18, 2011 at 9:38 AM, Mark Thomas ma...@apache.org wrote:
We have the option to move to svnpubsub for managing our releases.
Rather than copying artefacts to people.a.o and then waiting for rsync
(every around 2 hours) we would commit the artefacts to svn and a commit
hook
+1
On 05/18/2011 03:38 PM, Mark Thomas wrote:
If folks would like to go this route, I am happy to do the work on our
end to migrate /dist/tomcat to svnpubsub.
Regards
--
^TM
-
To unsubscribe, e-mail:
On 5/18/2011 9:22 AM, Mark Thomas wrote:
On 18/05/2011 15:06, Konstantin Kolinko wrote:
2011/5/18 Mark Thomas ma...@apache.org:
All,
We have the option to move to svnpubsub for managing our releases.
Rather than copying artefacts to people.a.o and then waiting for rsync
(every around 2
+1 to Marks proposal.
Shot additional answer to Konstantin inline.
On 18.05.2011 16:43, Konstantin Kolinko wrote:
Will the commit messages be forwarded to the mailing list?
At least the web server project does it like that. For an example see
+1
2011/5/18 Mark Thomas ma...@apache.org:
All,
We have the option to move to svnpubsub for managing our releases.
Rather than copying artefacts to people.a.o and then waiting for rsync
(every around 2 hours) we would commit the artefacts to svn and a commit
hook would update the
15 matches
Mail list logo
