You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by Ard Schrijvers <a....@onehippo.com> on 2012/07/06 17:39:40 UTC
[VOTE] Release Apache Jackrabbit OCM 2.0.0
Hi,
A candidate for Jackrabbit OCM 2.0.0 release is available at:
http://people.apache.org/~ard/ocm/2.0.0/
The release candidate is a zip archive of the sources in:
http://svn.apache.org/repos/asf/jackrabbit/commons/ocm/tags/jackrabbit-ocm-2.0.0/
The SHA1 checksum of the archive is 8e57c6b956ae271fa4df8cbe8d3e21a128ebc66e
A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachejackrabbit-035/
The commands for running automated checks against this release candidate are:
$ wget http://svn.apache.org/repos/asf/jackrabbit/commons/ocm/trunk/check-release.sh
$ sh check-release.sh ard 2.0.0 8e57c6b956ae271fa4df8cbe8d3e21a128ebc66e
Please vote on releasing this package as Apache Jackrabbit OCM 2.0.0
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.
[ ] +1 Release this package as Apache Jackrabbit OCM 2.0.0
[ ] -1 Do not release this package because...
+1 from me
Regards Ard
Re: [VOTE] Release Apache Jackrabbit OCM 2.0.0
Posted by Unico Homme <un...@apache.org>.
Checked and verified.
+1 Release this package as Apache Jackrabbit OCM 2.0.0
Great work Ard!
--
Unico
On Fri, Jul 6, 2012 at 5:39 PM, Ard Schrijvers <a....@onehippo.com>wrote:
> Hi,
>
> A candidate for Jackrabbit OCM 2.0.0 release is available at:
>
> http://people.apache.org/~ard/ocm/2.0.0/
>
> The release candidate is a zip archive of the sources in:
>
>
> http://svn.apache.org/repos/asf/jackrabbit/commons/ocm/tags/jackrabbit-ocm-2.0.0/
>
> The SHA1 checksum of the archive is
> 8e57c6b956ae271fa4df8cbe8d3e21a128ebc66e
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/content/repositories/orgapachejackrabbit-035/
>
> The commands for running automated checks against this release candidate
> are:
>
> $ wget
> http://svn.apache.org/repos/asf/jackrabbit/commons/ocm/trunk/check-release.sh
> $ sh check-release.sh ard 2.0.0
> 8e57c6b956ae271fa4df8cbe8d3e21a128ebc66e
>
> Please vote on releasing this package as Apache Jackrabbit OCM 2.0.0
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit OCM 2.0.0
> [ ] -1 Do not release this package because...
>
>
> +1 from me
>
> Regards Ard
>
Re: [VOTE] Release Apache Jackrabbit OCM 2.0.0
Posted by Michael Dürig <md...@apache.org>.
On 6.7.12 16:39, Ard Schrijvers wrote:
>
> [x] +1 Release this package as Apache Jackrabbit OCM 2.0.0
Thanks for putting this together!
Michael
Re: [DISCUSS] Re: Release Apache Jackrabbit OCM 2.0.0
Posted by Ard Schrijvers <a....@onehippo.com>.
Hello,
On Mon, Jul 9, 2012 at 11:46 AM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> [forking a separate discuss thread]
>
> On Mon, Jul 9, 2012 at 11:30 AM, Ard Schrijvers
> <a....@onehippo.com> wrote:
>> On Mon, Jul 9, 2012 at 10:51 AM, Bart van der Schans
>> <b....@onehippo.com> wrote:
>>> The src zip now contains a NOTICE.txt and NOTICE file as well as a
>>> LICENSE.txt as a LICENSE file.
>
> That's a consequence of using the source-release zip generated by the
> release profile as the release artifact. Even though it meets the
> formal Apache release guidelines, I'm not entirely happy with the way
> it's produced.
Well, I took a look at some other Apache project, took a look at
Jackrabbit and Oak, and thought I have the simplest project ever (just
a jar), so I thought that should be covered by the apache release
profile. Apparently not completely :)
>
> Instead, if you look at the main Jackrabbit or Oak trunk builds, there
> we have a custom assembly plugin configuration specified in the
> release profile:
>
> <plugin>
> <artifactId>maven-assembly-plugin</artifactId>
> <executions>
> <execution>
> <goals>
> <goal>single</goal>
> </goals>
> <phase>package</phase>
> <configuration>
> <descriptors>
> <descriptor>assembly.xml</descriptor>
> </descriptors>
> </configuration>
> </execution>
> <execution>
> <id>source-release-assembly</id>
> <configuration>
> <skipAssembly>true</skipAssembly>
> </configuration>
> </execution>
> </executions>
> </plugin>
>
> Basically this overrides the default source-release assembly
> (skipAssembly=true) defined in the Apache parent POM, and replaces it
> with a custom one defined in the assembly.xml descriptor that looks
> like this:
>
> <assembly>
> <id>src</id>
> <formats>
> <format>zip</format>
> </formats>
> <fileSets>
> <fileSet>
> <directory>${project.basedir}</directory>
> <outputDirectory></outputDirectory>
> <excludes>
> <exclude>**/target/**</exclude>
> <exclude>**/.*/**</exclude>
> </excludes>
> </fileSet>
> </fileSets>
> </assembly>
>
> The idea here is to copy everything in the current checkout, excluding
> generated files, so that the source archive ends up containing an
> exact copy of the sources that were used to generate the rest of the
> release. This is IMHO a better approach than the default
> source-release assembly that treats the source archive as another
> generated artifact that'll then get to include the autogenerated
> LICENSE/NOTICE/DEPENDENCIES files, a process that was originally
> designed just for binary artifacts..
I took a look at the Jackrabbit pom but thought that one was mainly
overriding the default source-release assembly because of sources
like the jackrabbit-standalone, jackrabbit-webapp, etc. Apparently
misunderstood that part.
>
>> I am not sure how to fix this. Should I remove the LICENCE.txt and
>> NOTICE.txt from svn? Or rename them to LICENCE and NOTICE?
>>
>> Also not sure about the DEPENDENCIES. Anybody?
>
> For now I'd just leave them in. For the next release I'd recommend
> going with the separate src assembly approach described above, as
> that'll take care of this.
I will do so, see [1]
>
>> Ah, that stupid derby.log file. I already explicitly ignored it in the
>> 'pedantic' profile. Not sure what the best way is to get rid of the
>> annoying derby.log file.. ideas are welcome
>
> The best solution to the derby.log file is to add the following
> configuration setting to the maven-surefire-plugin:
>
> <configuration>
> <systemProperties>
> <property>
> <name>derby.stream.error.file</name>
> <value>target/derby.log</value>
> </property>
> </systemProperties>
> </configuration>
>
> That way the derby.log file goes into target/ and won't clutter the
> rest of the checkout.
I great, thanks for the tip! See [2]
Regards Ard
[1] https://issues.apache.org/jira/browse/OCM-62
[2] https://issues.apache.org/jira/browse/OCM-63
>
> BR,
>
> Jukka Zitting
[DISCUSS] Re: Release Apache Jackrabbit OCM 2.0.0
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
[forking a separate discuss thread]
On Mon, Jul 9, 2012 at 11:30 AM, Ard Schrijvers
<a....@onehippo.com> wrote:
> On Mon, Jul 9, 2012 at 10:51 AM, Bart van der Schans
> <b....@onehippo.com> wrote:
>> The src zip now contains a NOTICE.txt and NOTICE file as well as a
>> LICENSE.txt as a LICENSE file.
That's a consequence of using the source-release zip generated by the
release profile as the release artifact. Even though it meets the
formal Apache release guidelines, I'm not entirely happy with the way
it's produced.
Instead, if you look at the main Jackrabbit or Oak trunk builds, there
we have a custom assembly plugin configuration specified in the
release profile:
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>single</goal>
</goals>
<phase>package</phase>
<configuration>
<descriptors>
<descriptor>assembly.xml</descriptor>
</descriptors>
</configuration>
</execution>
<execution>
<id>source-release-assembly</id>
<configuration>
<skipAssembly>true</skipAssembly>
</configuration>
</execution>
</executions>
</plugin>
Basically this overrides the default source-release assembly
(skipAssembly=true) defined in the Apache parent POM, and replaces it
with a custom one defined in the assembly.xml descriptor that looks
like this:
<assembly>
<id>src</id>
<formats>
<format>zip</format>
</formats>
<fileSets>
<fileSet>
<directory>${project.basedir}</directory>
<outputDirectory></outputDirectory>
<excludes>
<exclude>**/target/**</exclude>
<exclude>**/.*/**</exclude>
</excludes>
</fileSet>
</fileSets>
</assembly>
The idea here is to copy everything in the current checkout, excluding
generated files, so that the source archive ends up containing an
exact copy of the sources that were used to generate the rest of the
release. This is IMHO a better approach than the default
source-release assembly that treats the source archive as another
generated artifact that'll then get to include the autogenerated
LICENSE/NOTICE/DEPENDENCIES files, a process that was originally
designed just for binary artifacts..
> I am not sure how to fix this. Should I remove the LICENCE.txt and
> NOTICE.txt from svn? Or rename them to LICENCE and NOTICE?
>
> Also not sure about the DEPENDENCIES. Anybody?
For now I'd just leave them in. For the next release I'd recommend
going with the separate src assembly approach described above, as
that'll take care of this.
> Ah, that stupid derby.log file. I already explicitly ignored it in the
> 'pedantic' profile. Not sure what the best way is to get rid of the
> annoying derby.log file.. ideas are welcome
The best solution to the derby.log file is to add the following
configuration setting to the maven-surefire-plugin:
<configuration>
<systemProperties>
<property>
<name>derby.stream.error.file</name>
<value>target/derby.log</value>
</property>
</systemProperties>
</configuration>
That way the derby.log file goes into target/ and won't clutter the
rest of the checkout.
BR,
Jukka Zitting
Re: [VOTE] Release Apache Jackrabbit OCM 2.0.0
Posted by Ard Schrijvers <a....@onehippo.com>.
On Mon, Jul 9, 2012 at 10:51 AM, Bart van der Schans
<b....@onehippo.com> wrote:
> Hi,
>
> The check-release script complains about some differences between the
> svn tag and the code in the zip:
>
> $ diff -bur tag-svn/ tag-zip/
> Only in tag-zip/jackrabbit-ocm-2.0.0: DEPENDENCIES
> Only in tag-zip/jackrabbit-ocm-2.0.0: derby.log
> Only in tag-zip/jackrabbit-ocm-2.0.0: LICENSE
> Only in tag-zip/jackrabbit-ocm-2.0.0: NOTICE
>
> The src zip now contains a NOTICE.txt and NOTICE file as well as a
> LICENSE.txt as a LICENSE file.
Ah, when running the script I indeed also see the [error] (didn't
notice it before)
The DEPENDENCIES, LICENSE and NOTICE I assume are added by the
'apache-release' profile from the general apache pom.
I am not sure how to fix this. Should I remove the LICENCE.txt and
NOTICE.txt from svn? Or rename them to LICENCE and NOTICE?
Also not sure about the DEPENDENCIES. Anybody?
> It looks like the derby.log is a
> leftover from the build as it is not cleaned up by "mvn clean".
Ah, that stupid derby.log file. I already explicitly ignored it in the
'pedantic' profile. Not sure what the best way is to get rid of the
annoying derby.log file.. ideas are welcome
>
> I also think we need to update the check release script a little bit
> to verify all artifacts and not only the source zip file and check the
> pgp signing. I guess it should be easy enough to copy that from the
> jackrabbit check-release.sh script. The artifacts I checked manually
The check-release.sh script was copied from the jackrabbit one. There
are just not so many artifacts as you might expect. Perhaps you missed
this part:
[INFO] Step 2. Check individual files
[INFO] target/jackrabbit-ocm-staging-1341825237/jackrabbit-ocm-2.0.0-source-release.zip
gpg: ----
md5 : GOOD (7495daad93eaa2aa2a3b02960b791cf3)
sha : ----
> all seemed fine to me.
>
> The build works fine and all tests pass.
>
> So here is my +1! (unless the double NOTICE and LICENSE files have any
> legal consequences, but IANAL)
Thanks for the feedback Bart. I do want to 'fix' the NOTICE and
LICENSE duplication, as well as the DEPENDENCIES and derby.log in the
future (can't imagine it is a big deal now), but some feedback on best
practice is needed.
Regards Ard
>
> Thanks for all the work Ard!
>
> Bart
>
>
> On Fri, Jul 6, 2012 at 5:39 PM, Ard Schrijvers
> <a....@onehippo.com> wrote:
>> Hi,
>>
>> A candidate for Jackrabbit OCM 2.0.0 release is available at:
>>
>> http://people.apache.org/~ard/ocm/2.0.0/
>>
>> The release candidate is a zip archive of the sources in:
>>
>> http://svn.apache.org/repos/asf/jackrabbit/commons/ocm/tags/jackrabbit-ocm-2.0.0/
>>
>> The SHA1 checksum of the archive is 8e57c6b956ae271fa4df8cbe8d3e21a128ebc66e
>>
>> A staged Maven repository is available for review at:
>>
>> https://repository.apache.org/content/repositories/orgapachejackrabbit-035/
>>
>> The commands for running automated checks against this release candidate are:
>>
>> $ wget http://svn.apache.org/repos/asf/jackrabbit/commons/ocm/trunk/check-release.sh
>> $ sh check-release.sh ard 2.0.0 8e57c6b956ae271fa4df8cbe8d3e21a128ebc66e
>>
>> Please vote on releasing this package as Apache Jackrabbit OCM 2.0.0
>> The vote is open for the next 72 hours and passes if a majority of at
>> least three +1 Jackrabbit PMC votes are cast.
>>
>> [ ] +1 Release this package as Apache Jackrabbit OCM 2.0.0
>> [ ] -1 Do not release this package because...
>>
>>
>> +1 from me
>>
>> Regards Ard
>
>
>
> --
> Amsterdam - Oosteinde 11, 1017 WT Amsterdam
> Boston - 1 Broadway, Cambridge, MA 02142
>
> US +1 877 414 4776 (toll free)
> Europe +31(0)20 522 4466
> www.onehippo.com
--
Amsterdam - Oosteinde 11, 1017 WT Amsterdam
Boston - 1 Broadway, Cambridge, MA 02142
US +1 877 414 4776 (toll free)
Europe +31(0)20 522 4466
www.onehippo.com
Re: [VOTE] Release Apache Jackrabbit OCM 2.0.0
Posted by Bart van der Schans <b....@onehippo.com>.
Hi,
The check-release script complains about some differences between the
svn tag and the code in the zip:
$ diff -bur tag-svn/ tag-zip/
Only in tag-zip/jackrabbit-ocm-2.0.0: DEPENDENCIES
Only in tag-zip/jackrabbit-ocm-2.0.0: derby.log
Only in tag-zip/jackrabbit-ocm-2.0.0: LICENSE
Only in tag-zip/jackrabbit-ocm-2.0.0: NOTICE
The src zip now contains a NOTICE.txt and NOTICE file as well as a
LICENSE.txt as a LICENSE file. It looks like the derby.log is a
leftover from the build as it is not cleaned up by "mvn clean".
I also think we need to update the check release script a little bit
to verify all artifacts and not only the source zip file and check the
pgp signing. I guess it should be easy enough to copy that from the
jackrabbit check-release.sh script. The artifacts I checked manually
all seemed fine to me.
The build works fine and all tests pass.
So here is my +1! (unless the double NOTICE and LICENSE files have any
legal consequences, but IANAL)
Thanks for all the work Ard!
Bart
On Fri, Jul 6, 2012 at 5:39 PM, Ard Schrijvers
<a....@onehippo.com> wrote:
> Hi,
>
> A candidate for Jackrabbit OCM 2.0.0 release is available at:
>
> http://people.apache.org/~ard/ocm/2.0.0/
>
> The release candidate is a zip archive of the sources in:
>
> http://svn.apache.org/repos/asf/jackrabbit/commons/ocm/tags/jackrabbit-ocm-2.0.0/
>
> The SHA1 checksum of the archive is 8e57c6b956ae271fa4df8cbe8d3e21a128ebc66e
>
> A staged Maven repository is available for review at:
>
> https://repository.apache.org/content/repositories/orgapachejackrabbit-035/
>
> The commands for running automated checks against this release candidate are:
>
> $ wget http://svn.apache.org/repos/asf/jackrabbit/commons/ocm/trunk/check-release.sh
> $ sh check-release.sh ard 2.0.0 8e57c6b956ae271fa4df8cbe8d3e21a128ebc66e
>
> Please vote on releasing this package as Apache Jackrabbit OCM 2.0.0
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
>
> [ ] +1 Release this package as Apache Jackrabbit OCM 2.0.0
> [ ] -1 Do not release this package because...
>
>
> +1 from me
>
> Regards Ard
--
Amsterdam - Oosteinde 11, 1017 WT Amsterdam
Boston - 1 Broadway, Cambridge, MA 02142
US +1 877 414 4776 (toll free)
Europe +31(0)20 522 4466
www.onehippo.com
Re: [VOTE] Release Apache Jackrabbit OCM 2.0.0
Posted by Ard Schrijvers <a....@onehippo.com>.
On Tue, Sep 4, 2012 at 3:31 PM, Michael Dürig <md...@apache.org> wrote:
>
> On 4.9.12 14:09, Ard Schrijvers wrote:
>
> Hi Ards,
>
>
>>> Hi,
>>>
>>> What is the state of this? I can see from
>>> http://archive.apache.org/dist/jackrabbit/ocm/2.0.0/ that the release is
>>> there but never saw an announcement on the list not can I see it listed
>>> on
>>> the Jackrabbit web site. Can we consider OCM 2.0.0 released? Otherwise
>>> what
>>> are the missing bits to make it happen?
>>
>>
>> This is completely my bad, apologies! I can't really recall but it
>> must have slipped my mind to actually announce the 2.0.0 release. I'll
>> send out an announcement today to the public list, ok?
>
>
> No problem. I just stumbled on this while preparing the board report. Having
> an official announcement would be great!
>
>
>>
>> Regarding the website : Should I only include the info at [1] or also
>> at [2]. I am not sure whether the release notes from ocm belong at
>> [2]. Do you have a suggestion?
>
>
> Unless others object, I'd include this in both places. To me [2] is about
> all the releases of Jackrabbit. This may well include its sub projects.
Ok. All I need more is write access :)
Regards Ard
>
> Michael
>
>
>>
>> Regards Ard
>>
>> [1] http://jackrabbit.apache.org/object-content-mapping.html
>> [2] http://jackrabbit.apache.org/downloads.html
>>>
>>>
>>> Michael
>>>
>>>
>>>>
>>>> Regards Ard
>>>>
>>>> [1] https://issues.apache.org/jira/browse/OCM-62 : Improve pom to
>>>> align releases with the Jackrabbit assembly plugin configuration
>>>> [2] https://issues.apache.org/jira/browse/OCM-63 : Make sure derby.log
>>>> ends up in target dir
>>>>
>>>
>>
>>
>>
>
--
Amsterdam - Oosteinde 11, 1017 WT Amsterdam
Boston - 1 Broadway, Cambridge, MA 02142
US +1 877 414 4776 (toll free)
Europe +31(0)20 522 4466
www.onehippo.com
Re: [VOTE] Release Apache Jackrabbit OCM 2.0.0
Posted by Michael Dürig <md...@apache.org>.
On 4.9.12 14:09, Ard Schrijvers wrote:
Hi Ards,
>> Hi,
>>
>> What is the state of this? I can see from
>> http://archive.apache.org/dist/jackrabbit/ocm/2.0.0/ that the release is
>> there but never saw an announcement on the list not can I see it listed on
>> the Jackrabbit web site. Can we consider OCM 2.0.0 released? Otherwise what
>> are the missing bits to make it happen?
>
> This is completely my bad, apologies! I can't really recall but it
> must have slipped my mind to actually announce the 2.0.0 release. I'll
> send out an announcement today to the public list, ok?
No problem. I just stumbled on this while preparing the board report.
Having an official announcement would be great!
>
> Regarding the website : Should I only include the info at [1] or also
> at [2]. I am not sure whether the release notes from ocm belong at
> [2]. Do you have a suggestion?
Unless others object, I'd include this in both places. To me [2] is
about all the releases of Jackrabbit. This may well include its sub
projects.
Michael
>
> Regards Ard
>
> [1] http://jackrabbit.apache.org/object-content-mapping.html
> [2] http://jackrabbit.apache.org/downloads.html
>>
>> Michael
>>
>>
>>>
>>> Regards Ard
>>>
>>> [1] https://issues.apache.org/jira/browse/OCM-62 : Improve pom to
>>> align releases with the Jackrabbit assembly plugin configuration
>>> [2] https://issues.apache.org/jira/browse/OCM-63 : Make sure derby.log
>>> ends up in target dir
>>>
>>
>
>
>
Re: [VOTE] Release Apache Jackrabbit OCM 2.0.0
Posted by Ard Schrijvers <a....@onehippo.com>.
Hello Michael,
On Tue, Sep 4, 2012 at 2:56 PM, Michael Dürig <md...@apache.org> wrote:
>
>
> On 10.7.12 16:39, Ard Schrijvers wrote:
>>
>> On Fri, Jul 6, 2012 at 5:39 PM, Ard Schrijvers
>> <a....@onehippo.com> wrote:
>>>
>>>
>>> Please vote on releasing this package as Apache Jackrabbit OCM 2.0.0
>>
>>
>> The vote passes as follows:
>>
>> +1 Ard Schrijvers
>> +1 Unico Hommes
>> +1 Michael Dürig
>> +1 Bart van der Schans
>> +1 Jukka Zitting
>>
>> Thanks for voting, thanks for the feedback regarding the release (see
>> [1] and [2] for next iteration improvements), and I'll push out the
>> release
>
>
> Hi,
>
> What is the state of this? I can see from
> http://archive.apache.org/dist/jackrabbit/ocm/2.0.0/ that the release is
> there but never saw an announcement on the list not can I see it listed on
> the Jackrabbit web site. Can we consider OCM 2.0.0 released? Otherwise what
> are the missing bits to make it happen?
This is completely my bad, apologies! I can't really recall but it
must have slipped my mind to actually announce the 2.0.0 release. I'll
send out an announcement today to the public list, ok?
Regarding the website : Should I only include the info at [1] or also
at [2]. I am not sure whether the release notes from ocm belong at
[2]. Do you have a suggestion?
Regards Ard
[1] http://jackrabbit.apache.org/object-content-mapping.html
[2] http://jackrabbit.apache.org/downloads.html
>
> Michael
>
>
>>
>> Regards Ard
>>
>> [1] https://issues.apache.org/jira/browse/OCM-62 : Improve pom to
>> align releases with the Jackrabbit assembly plugin configuration
>> [2] https://issues.apache.org/jira/browse/OCM-63 : Make sure derby.log
>> ends up in target dir
>>
>
--
Amsterdam - Oosteinde 11, 1017 WT Amsterdam
Boston - 1 Broadway, Cambridge, MA 02142
US +1 877 414 4776 (toll free)
Europe +31(0)20 522 4466
www.onehippo.com
Re: [VOTE] Release Apache Jackrabbit OCM 2.0.0
Posted by Michael Dürig <md...@apache.org>.
On 10.7.12 16:39, Ard Schrijvers wrote:
> On Fri, Jul 6, 2012 at 5:39 PM, Ard Schrijvers
> <a....@onehippo.com> wrote:
>>
>> Please vote on releasing this package as Apache Jackrabbit OCM 2.0.0
>
> The vote passes as follows:
>
> +1 Ard Schrijvers
> +1 Unico Hommes
> +1 Michael Dürig
> +1 Bart van der Schans
> +1 Jukka Zitting
>
> Thanks for voting, thanks for the feedback regarding the release (see
> [1] and [2] for next iteration improvements), and I'll push out the
> release
Hi,
What is the state of this? I can see from
http://archive.apache.org/dist/jackrabbit/ocm/2.0.0/ that the release is
there but never saw an announcement on the list not can I see it listed
on the Jackrabbit web site. Can we consider OCM 2.0.0 released?
Otherwise what are the missing bits to make it happen?
Michael
>
> Regards Ard
>
> [1] https://issues.apache.org/jira/browse/OCM-62 : Improve pom to
> align releases with the Jackrabbit assembly plugin configuration
> [2] https://issues.apache.org/jira/browse/OCM-63 : Make sure derby.log
> ends up in target dir
>
Re: [VOTE] Release Apache Jackrabbit OCM 2.0.0
Posted by Ard Schrijvers <a....@onehippo.com>.
On Fri, Jul 6, 2012 at 5:39 PM, Ard Schrijvers
<a....@onehippo.com> wrote:
>
> Please vote on releasing this package as Apache Jackrabbit OCM 2.0.0
The vote passes as follows:
+1 Ard Schrijvers
+1 Unico Hommes
+1 Michael Dürig
+1 Bart van der Schans
+1 Jukka Zitting
Thanks for voting, thanks for the feedback regarding the release (see
[1] and [2] for next iteration improvements), and I'll push out the
release
Regards Ard
[1] https://issues.apache.org/jira/browse/OCM-62 : Improve pom to
align releases with the Jackrabbit assembly plugin configuration
[2] https://issues.apache.org/jira/browse/OCM-63 : Make sure derby.log
ends up in target dir
Re: [VOTE] Release Apache Jackrabbit OCM 2.0.0
Posted by Ard Schrijvers <a....@onehippo.com>.
On Mon, Jul 9, 2012 at 12:18 PM, Jukka Zitting <ju...@gmail.com> wrote:
>
> What I meant instead is the .asc file that contains your signature for
> the specific release archive. Currently
> http://people.apache.org/~ard/ocm/2.0.0/ only comes with the MD5 and
> SHA1 checksums.
I've added ths .asc as well [1]
Thanks for the pointer Jukka
Regards Ard
[1] http://people.apache.org/~ard/ocm/2.0.0/jackrabbit-ocm-2.0.0-source-release.zip.asc
>
> BR,
>
> Jukka Zitting
--
Amsterdam - Oosteinde 11, 1017 WT Amsterdam
Boston - 1 Broadway, Cambridge, MA 02142
US +1 877 414 4776 (toll free)
Europe +31(0)20 522 4466
www.onehippo.com
Re: [VOTE] Release Apache Jackrabbit OCM 2.0.0
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Mon, Jul 9, 2012 at 12:13 PM, Ard Schrijvers
<a....@onehippo.com> wrote:
> Isn't the source zip available at [1] not the way it is normally also
> done by you?
No, see the [DISCUSS] thread I started.
> Regarding the PGP signature: Do you mean I should create a KEYS file
> at ~ard like you have your KEYS file at [2] ?
We already have the KEYS file in
http://svn.apache.org/repos/asf/jackrabbit/dist/ and
http://www.apache.org/dist/jackrabbit/ so it isn't needed to go with
each individual release.
What I meant instead is the .asc file that contains your signature for
the specific release archive. Currently
http://people.apache.org/~ard/ocm/2.0.0/ only comes with the MD5 and
SHA1 checksums.
BR,
Jukka Zitting
Re: [VOTE] Release Apache Jackrabbit OCM 2.0.0
Posted by Ard Schrijvers <a....@onehippo.com>.
On Mon, Jul 9, 2012 at 11:33 AM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> On Fri, Jul 6, 2012 at 5:39 PM, Ard Schrijvers
> <a....@onehippo.com> wrote:
>> Please vote on releasing this package as Apache Jackrabbit OCM 2.0.0
>
> [x] +1 Release this package as Apache Jackrabbit OCM 2.0.0
>
> PS. You should make the PGP signature available with the source zip
> file also outside the staged Maven repository.
Isn't the source zip available at [1] not the way it is normally also
done by you?
Regarding the PGP signature: Do you mean I should create a KEYS file
at ~ard like you have your KEYS file at [2] ?
[1] http://people.apache.org/~ard/ocm/2.0.0/
[2] http://people.apache.org/~jukka/jackrabbit/
Regards Ard
>
> BR,
>
> Jukka Zitting
--
Amsterdam - Oosteinde 11, 1017 WT Amsterdam
Boston - 1 Broadway, Cambridge, MA 02142
US +1 877 414 4776 (toll free)
Europe +31(0)20 522 4466
www.onehippo.com
Re: [VOTE] Release Apache Jackrabbit OCM 2.0.0
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Fri, Jul 6, 2012 at 5:39 PM, Ard Schrijvers
<a....@onehippo.com> wrote:
> Please vote on releasing this package as Apache Jackrabbit OCM 2.0.0
[x] +1 Release this package as Apache Jackrabbit OCM 2.0.0
PS. You should make the PGP signature available with the source zip
file also outside the staged Maven repository.
BR,
Jukka Zitting