Non-PMC members can certainly make releases. I would suggest at
present just clarify step 15 to say "update, or ask for someone to
update".
The board report is in a private area on the off chance that something
non-public needs to be included. However such a thing would need to be
appropr
2008/10/11 Barrie Treloar <[EMAIL PROTECTED]>:
> On Sun, Oct 12, 2008 at 10:27 AM, Vincent Siveton
> <[EMAIL PROTECTED]> wrote:
>> I am saying that the PMC should take care of all releases (PMC or
>> not), and then update this file.
>>
>> Hope that it is clear.
>>
>
> Ok,
> I don't care either way,
On Sun, Oct 12, 2008 at 10:27 AM, Vincent Siveton
<[EMAIL PROTECTED]> wrote:
> I am saying that the PMC should take care of all releases (PMC or
> not), and then update this file.
>
> Hope that it is clear.
>
Ok,
I don't care either way, but developers/release/releasing.html needs
to be updated to
I am saying that the PMC should take care of all releases (PMC or
not), and then update this file.
Hope that it is clear.
Vincent
2008/10/11 Barrie Treloar <[EMAIL PROTECTED]>:
>>> Thanks.
>>> I'm starting to wonder whether the release process should also be PMC only.
>>> A committer can do ever
On Sun, Oct 12, 2008 at 10:15 AM, Barrie Treloar <[EMAIL PROTECTED]> wrote:
>>> Thanks.
>>> I'm starting to wonder whether the release process should also be PMC only.
>>> A committer can do every step except this one.
>>>
>>> What is the process to get this file updated?
>>> Email the dev list wit
>> Thanks.
>> I'm starting to wonder whether the release process should also be PMC only.
>> A committer can do every step except this one.
>>
>> What is the process to get this file updated?
>> Email the dev list with the request?
>
> IMHO nope, it is the responsibility of the PMC to do this.
Are
Hi again,
2008/10/11 Barrie Treloar <[EMAIL PROTECTED]>:
> On Sun, Oct 12, 2008 at 9:19 AM, Vincent Siveton
> <[EMAIL PROTECTED]> wrote:
>> Hi again,
>>
>> Yes it is only for PMC. I did it.
>
> Thanks.
> I'm starting to wonder whether the release process should also be PMC only.
> A committer can
On Sun, Oct 12, 2008 at 9:19 AM, Vincent Siveton
<[EMAIL PROTECTED]> wrote:
> Hi again,
>
> Yes it is only for PMC. I did it.
Thanks.
I'm starting to wonder whether the release process should also be PMC only.
A committer can do every step except this one.
What is the process to get this file upd
On Sun, Oct 12, 2008 at 9:17 AM, Vincent Siveton
<[EMAIL PROTECTED]> wrote:
> Hi Barrie,
>
> Just update the file in svn.
Vincent pointed out the files are in the site project
https://svn.apache.org/repos/asf/maven/site/trunk/src/site/apt/plugins/index.apt
On Sun, Oct 12, 2008 at 9:17 AM, Vincent Siveton
<[EMAIL PROTECTED]> wrote:
> Hi Barrie,
>
> Just update the file in svn.
>
> Cheers,
Thanks.
I've update the page with extra steps from the perspective of someone
who hasn't done it before.
--
Hi again,
Yes it is only for PMC. I did it.
Cheers,
Vincent
2008/10/11 Barrie Treloar <[EMAIL PROTECTED]>:
> Where is the private subversion area?
> Is this a PMC only step?
>
> Step 15 Add the release to the next board report, in the private
> subversion area.
>
> -
Hi Barrie,
Just update the file in svn.
Cheers,
Vincent
2008/10/11 Barrie Treloar <[EMAIL PROTECTED]>:
> How do I do the following?
> Do I edit the file directly from people.apache.org or do I make the
> changes in subversion?
>
> Step 12. Update the index page
>
> If this is a plugin release,
Where is the private subversion area?
Is this a PMC only step?
Step 15 Add the release to the next board report, in the private
subversion area.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
How do I do the following?
Do I edit the file directly from people.apache.org or do I make the
changes in subversion?
Step 12. Update the index page
If this is a plugin release, update the version number for the plugin
on the /plugins/index.html page.
If this is a shared component release, updat
The Maven team is pleased to announce the release of the Maven Antrun
Plugin, version 1.3
This plugin provides the ability to run Ant tasks from within Maven 2.
http://maven.apache.org/plugins/maven-antrun-plugin/
You should specify the version in your project's plugin configuration:
org.apac
On Sun, Oct 12, 2008 at 1:57 AM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] ~]$ find
> /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/maven
> -name '*.rip' -print
> /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/maven/plugins/maven-antrun-plu
On Sun, Oct 12, 2008 at 1:28 AM, Hervé BOUTEMY <[EMAIL PROTECTED]> wrote:
>> find . -type d -exec chmod a+rx {} \;
>> find . -type d -exec chmod g+w {} \;
>> find . -type f -exec chmod 664 {} \;
>>
>> Can't this be replaced with
>>
>> chmod -R a+rX,g+w,o-w /www/maven.apache.org/plugins/maven-XXX-pl
[EMAIL PROTECTED] ~]$ find
/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/maven
-name '*.rip' -print
/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/maven/plugins/maven-antrun-plugin/1.3/1.3.rip
This one is now in central :
http://repo1.maven.org/maven2/org/
+1
easier and more efficient
Le lundi 06 octobre 2008, Barrie Treloar a écrit :
> Verify/change folder permissions to 0775 and files permissions to 0664
> i.e.:
>
> find . -type d -exec chmod a+rx {} \;
> find . -type d -exec chmod g+w {} \;
> find . -type f -exec chmod 664 {} \;
>
> Can't this be
On Sat, Oct 11, 2008 at 9:29 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> Oops my bad it looks there is some files with bad permissions in
> org/apache/maven/plugins :
>
> -rw-r--r-- 1 olamy apcvs40 Sep 29 13:26 maven-metadata.xml.sha1
> -rw-r--r-- 1 olamy apcvs32 Sep 29 13:2
Oops my bad it looks there is some files with bad permissions in
org/apache/maven/plugins :
-rw-r--r-- 1 olamy apcvs40 Sep 29 13:26 maven-metadata.xml.sha1
-rw-r--r-- 1 olamy apcvs32 Sep 29 13:26 maven-metadata.xml.md5
-rw-r--r-- 1 olamy apcvs 6859 Sep 29 13:26 maven-
On 11/10/2008, at 9:36 PM, Barrie Treloar wrote:
On Sat, Oct 11, 2008 at 6:40 PM, Barrie Treloar <[EMAIL PROTECTED]>
wrote:
Hi,
The vote has passed with the following result :
+1 (binding): Oliver Lamy, Brett Porter, Stephane Nicoll, Vincent
Siveton
+1 (non binding):
I will move artifact
On Sat, Oct 11, 2008 at 6:40 PM, Barrie Treloar <[EMAIL PROTECTED]> wrote:
> Hi,
> The vote has passed with the following result :
>
> +1 (binding): Oliver Lamy, Brett Porter, Stephane Nicoll, Vincent Siveton
> +1 (non binding):
>
> I will move artifacts to central repo.
>
I had the java.lang.Clas
Hi,
The vote has passed with the following result :
+1 (binding): Oliver Lamy, Brett Porter, Stephane Nicoll, Vincent Siveton
+1 (non binding):
I will move artifacts to central repo.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
F
24 matches
Mail list logo
