[Vote] Release Doxia-1.1.1 and Doxia-Sitetools-1.1.1 (take two)

[Lukas Theussl-4]

Hi again,

We have cranked some more 23 issues into this release since the last failed
attempt, so now we're at 47 (Doxia) and 6 (Sitetools) solved issues:

http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780&styleName=Html&version=15073
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11624&styleName=Html&version=15075

There are still a couple of issues left in JIRA:

http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10780&status=1
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11624&status=1

Staging repos:
https://repository.apache.org/content/repositories/maven-staging-019/
https://repository.apache.org/content/repositories/maven-staging-020/

Staging sites:
http://maven.apache.org/doxia/doxia/
http://maven.apache.org/doxia/doxia-sitetools/

(I have deployed to the main sites as nothing major has changed wrt 1.1 and I
can't use site:stage because of MSITE-404)

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html


Note: the most convenient way to test (I think) is to use site-plugin-2.1-SNAPSHOT
and/or pdf-plugin-1.0-SNAPSHOT, which both use the latest doxia snaps.


Vote is open for 72 hours.

[x] +1
[ ] +0
[ ] -1


Thanks,
-Lukas



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[nicolas de loof-2]

+1
Tested with the PDF plugin to generate gwt-maven-plugin doc -> works fine ;)

2009/6/18 Lukas Theussl <ltheussl@...>

>
> Hi again,
>
> We have cranked some more 23 issues into this release since the last failed
> attempt, so now we're at 47 (Doxia) and 6 (Sitetools) solved issues:
>
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780&styleName=Html&version=15073
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11624&styleName=Html&version=15075
>
> There are still a couple of issues left in JIRA:
>
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10780&status=1
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11624&status=1
>
> Staging repos:
> https://repository.apache.org/content/repositories/maven-staging-019/
> https://repository.apache.org/content/repositories/maven-staging-020/
>
> Staging sites:
> http://maven.apache.org/doxia/doxia/
> http://maven.apache.org/doxia/doxia-sitetools/
>
> (I have deployed to the main sites as nothing major has changed wrt 1.1 and
> I can't use site:stage because of MSITE-404)
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
>
> Note: the most convenient way to test (I think) is to use
> site-plugin-2.1-SNAPSHOT and/or pdf-plugin-1.0-SNAPSHOT, which both use the
> latest doxia snaps.
>
>
> Vote is open for 72 hours.
>
> [x] +1
> [ ] +0
> [ ] -1
>
>
> Thanks,
> -Lukas
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

[Vincent Siveton]

+1

Additional notice: we added source releases to respect the ASF release
requirements.

Vincent

2009/6/18 Lukas Theussl <ltheussl@...>:

>
> Hi again,
>
> We have cranked some more 23 issues into this release since the last failed
> attempt, so now we're at 47 (Doxia) and 6 (Sitetools) solved issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780&styleName=Html&version=15073
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11624&styleName=Html&version=15075
>
> There are still a couple of issues left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10780&status=1
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11624&status=1
>
> Staging repos:
> https://repository.apache.org/content/repositories/maven-staging-019/
> https://repository.apache.org/content/repositories/maven-staging-020/
>
> Staging sites:
> http://maven.apache.org/doxia/doxia/
> http://maven.apache.org/doxia/doxia-sitetools/
>
> (I have deployed to the main sites as nothing major has changed wrt 1.1 and
> I can't use site:stage because of MSITE-404)
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
>
> Note: the most convenient way to test (I think) is to use
> site-plugin-2.1-SNAPSHOT and/or pdf-plugin-1.0-SNAPSHOT, which both use the
> latest doxia snaps.
>
>
> Vote is open for 72 hours.
>
> [x] +1
> [ ] +0
> [ ] -1
>
>
> Thanks,
> -Lukas
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Benjamin Bentmann]

Lukas Theussl wrote:

> Staging repos:
> https://repository.apache.org/content/repositories/maven-staging-019/
> https://repository.apache.org/content/repositories/maven-staging-020/

+1 in general, only the signatures for the POMs would need to be
double-checked and fixed. This release was apparently made with Maven
2.1.0 and hence POMs like doxia-1.1.1.pom and doxia-sitetools-1.1.1.pom
suffer from MGPG-14.

This release provides source-release packages for each individual sub
module. Is that a strict requirement by ASF policy or didn't we conclude
that a single source-release for the root project would be sufficient?


Benjamin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[brettporter]

On 21/06/2009, at 9:43 PM, Benjamin Bentmann wrote:

> Lukas Theussl wrote:
>
>> Staging repos:
>> https://repository.apache.org/content/repositories/maven-staging-019/
>> https://repository.apache.org/content/repositories/maven-staging-020/
>
> +1 in general, only the signatures for the POMs would need to be  
> double-checked and fixed. This release was apparently made with  
> Maven 2.1.0 and hence POMs like doxia-1.1.1.pom and doxia-
> sitetools-1.1.1.pom suffer from MGPG-14.
>
> This release provides source-release packages for each individual  
> sub module. Is that a strict requirement by ASF policy or didn't we  
> conclude that a single source-release for the root project would be  
> sufficient?

I think either is sufficient, as long as there is a complete,  
buildable source release for every part. I would prefer to have one  
source bundle per vote where the release schedule is tied together.

- Brett


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Lukas Theussl-4]

Benjamin Bentmann wrote:

> Lukas Theussl wrote:
>
>> Staging repos:
>> https://repository.apache.org/content/repositories/maven-staging-019/
>> https://repository.apache.org/content/repositories/maven-staging-020/
>
> +1 in general, only the signatures for the POMs would need to be
> double-checked and fixed. This release was apparently made with Maven
> 2.1.0 and hence POMs like doxia-1.1.1.pom and doxia-sitetools-1.1.1.pom
> suffer from MGPG-14.

The signatures are wrong indeed, thanks for spotting this. I believe this can be
fixed on the repo side so I don't want to stop the release just yet unless I can't
find anybody (Brian?) to fix it, or it's deemed too much hassle or anybody has
another objection.

>
> This release provides source-release packages for each individual sub
> module. Is that a strict requirement by ASF policy or didn't we conclude
> that a single source-release for the root project would be sufficient?

As I understand, it's not necessary but doesn't hurt. I won't do it next time
anymore though as it's just unnecessary overhead. I also think that one source
bundle for the top-parent artifact, where everything can be built from, should be
enough.

Thanks,
-Lukas

>
>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Lukas Theussl-4]

Ok, the signatures are fixed in the staging repo, thanks to Brian, so I'd say we
call it a release. The voting period has passed and we have 3 binding +1 (Vincent,
Benjamin, myself), plus one non-binding (Nicolas).

I'll wait a few more hours before promoting the artifacts if anybody wants to
re-check the signatures, but the vote is formally closed now.

Thanks,
-Lukas


Lukas Theussl wrote:

>
> Hi again,
>
> We have cranked some more 23 issues into this release since the last
> failed attempt, so now we're at 47 (Doxia) and 6 (Sitetools) solved issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780&styleName=Html&version=15073 
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11624&styleName=Html&version=15075 
>
>
> There are still a couple of issues left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10780&status=1 
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11624&status=1 
>
>
> Staging repos:
> https://repository.apache.org/content/repositories/maven-staging-019/
> https://repository.apache.org/content/repositories/maven-staging-020/
>
> Staging sites:
> http://maven.apache.org/doxia/doxia/
> http://maven.apache.org/doxia/doxia-sitetools/
>
> (I have deployed to the main sites as nothing major has changed wrt 1.1
> and I can't use site:stage because of MSITE-404)
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
>
> Note: the most convenient way to test (I think) is to use
> site-plugin-2.1-SNAPSHOT and/or pdf-plugin-1.0-SNAPSHOT, which both use
> the latest doxia snaps.
>
>
> Vote is open for 72 hours.
>
> [x] +1
> [ ] +0
> [ ] -1
>
>
> Thanks,
> -Lukas
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...