Hi,
The vote passes as follows:
+1 Marcel Reutegger
+1 Cédric Damioli
+1 KÖLL Claus
+1 Amit Jain
Thanks for voting. I'll push the release out.
Regards
Amit
On Wed, Mar 23, 2016 at 10:18 PM, Davide Giannella
wrote:
> A candidate for the Jackrabbit 2.10.2 release is
+1
greets
claus
[INFO]
[INFO] ALL CHECKS OK
[INFO]
[X] +1 Release this package as Apache Jackrabbit 2.10.2
[ ] -1 Do not release this package because...
On 23/03/16 17:48, "Davide Giannella" wrote:
>Please vote on releasing this package as Apache Jackrabbit 2.10.2.
>The vote is open for the next 72 hours and passes if a majority of at
>least three +1 Jackrabbit PMC votes are cast.
All checks OK.
+1 Release this package as Apache Jackrabbit
Hi,
Since, the voting period overlapped with the long weekend we should we
extend the vote another 72 hours.
Thanks
Amit
On Wed, Mar 23, 2016 at 10:18 PM, Davide Giannella
wrote:
> A candidate for the Jackrabbit 2.10.2 release is available at:
>
>
On Wed, Mar 23, 2016 at 10:18 PM, Davide Giannella
wrote:
>
> Please vote on releasing this package as Apache Jackrabbit 2.10.2.
> 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
[X] +1 Release this package as Apache Jackrabbit 2.10.2
Davide
A candidate for the Jackrabbit 2.10.2 release is available at:
https://dist.apache.org/repos/dist/dev/jackrabbit/2.10.2/
The release candidate is a zip archive of the sources in:
https://svn.apache.org/repos/asf/jackrabbit/tags/2.10.2/
The SHA1 checksum of the archive is
Hi,
I've created a branch for 2.10.x [1]. The version number is back to
2.10.2-SNAPSHOT. Commits on JCR-3880, JCR-3885, and JCR-3894 have been
reverted on the new 2.10 branch because they contained changes to the
api. The fix version of these issues has been updated to 2.11.0. The
trunk is now on
Hi Davide,
With regard to creating a branch, if you want I can do that for you,
as well as the related tasks of creating the JIRA versions, reverting
the relevant commits on the branch, etc. Let me know if you want any
help.
--
Unico
On Mon, Aug 10, 2015 at 9:05 AM, Davide Giannella
Hello Team,
the vote DOESN'T pass as follows
-1 Davide Giannella
-1 Unico Hommes
-1 Bart van der Schans
Thanks for voting. I'll proceed with deletes and drops
-- Davide
Good point. I'll take care of it during the branching.
--
Unico
On Mon, Aug 10, 2015 at 3:28 PM, Davide Giannella dav...@apache.org wrote:
On 10/08/2015 09:05, Davide Giannella wrote:
Hello Team,
the vote DOESN'T pass as follows
-1 Davide Giannella
-1 Unico Hommes
-1 Bart van der Schans
On 10/08/2015 10:49, Unico Hommes wrote:
Hi Davide,
With regard to creating a branch, if you want I can do that for you,
as well as the related tasks of creating the JIRA versions, reverting
the relevant commits on the branch, etc. Let me know if you want any
help.
If you could take care of
On 10/08/2015 09:05, Davide Giannella wrote:
Hello Team,
the vote DOESN'T pass as follows
-1 Davide Giannella
-1 Unico Hommes
-1 Bart van der Schans
Thanks for voting. I'll proceed with deletes and drops
It's not mentioned on the release-steps, but shall I revert the JR poms
to
The new branch location:
http://svn.apache.org/repos/asf/jackrabbit/branches/2.10/
On Mon, Aug 10, 2015 at 4:19 PM, Unico Hommes un...@apache.org wrote:
Hi,
I've created a branch for 2.10.x [1]. The version number is back to
2.10.2-SNAPSHOT. Commits on JCR-3880, JCR-3885, and JCR-3894 have
On 6.8.15 10:51 , Angela Schreiber wrote:
hi
-1 for reverting the changes. i only applied them to the
trunk (and not to a released branch, which i never intended
to do) and i don't see any reason why extending the API should
not be possible there.
This is only about reverting so we can
Hi Chetan,
On Thu, Aug 6, 2015 at 11:00 AM, Chetan Mehrotra
chetan.mehro...@gmail.com wrote:
On Thu, Aug 6, 2015 at 2:21 PM, Angela Schreiber anch...@adobe.com wrote:
i am fine...
quite frankly i am surprised to see that there is no 2.10
branch.
I think this was discussed earlier [1]. Looks
On Thu, Aug 6, 2015 at 10:51 AM, Angela Schreiber anch...@adobe.com wrote:
hi
-1 for reverting the changes. i only applied them to the
trunk (and not to a released branch, which i never intended
to do) and i don't see any reason why extending the API should
not be possible there.
the
hi
ok i see... as long as my improvmeents stay (or get properly
reapplied) on jackrabbit trunk and get released with the
next (instable) 2.x.y, i am all fine and don't mind
about the details on how we get there... i just don't want
to run after a broken oak.
what we also might want to consider
On Thu, Aug 6, 2015 at 2:21 PM, Angela Schreiber anch...@adobe.com wrote:
i am fine...
quite frankly i am surprised to see that there is no 2.10
branch.
I think this was discussed earlier [1]. Looks like we would have to
revisit that decision and continue with stable/unstable releases
Chetan
[X] -1 Do not release this package because...
it says
svn: E17: URL
'https://svn.apache.org/repos/asf/jackrabbit/tags/2.10.2' doesn't exist
and indeed it doesn't. By looking at SVN I can find that since 2.10.1
the tag created are `jackrabbit-VERSION` rather than `VERSION`.
I searched
Hi Davide,
2.10.1 was mistakenly tagged as jackrabbit-2.10.1 and maybe that carried
over.
Not sure whether its an option here but can't we just rename the tag in
svn?
Thanks
Amit
On Wed, Aug 5, 2015 at 12:25 PM, Davide Giannella dav...@apache.org wrote:
[X] -1 Do not release this package
On 05/08/2015 10:01, Amit Jain wrote:
Hi Davide,
2.10.1 was mistakenly tagged as jackrabbit-2.10.1 and maybe that
carried over.
Not sure whether its an option here but can't we just rename the tag
in svn?
Theoretically possible by something like
svn mv \
I'm also -1 on this release but for a different reason.
It seems that there are (again) API changes in a maintenance tag [1].
I've already indicated that I don't agree with this procedure. That
API changes need to be made on a 2.12 branch only.
1. Changesets 1694048 and 1693235
2.
On 05/08/2015 14:27, Davide Giannella wrote:
On 05/08/2015 10:01, Amit Jain wrote:
Hi Davide,
2.10.1 was mistakenly tagged as jackrabbit-2.10.1 and maybe that
carried over.
Not sure whether its an option here but can't we just rename the tag
in svn?
Theoretically possible by something
Hi guys,
I really have to agree with Unico here. We should not make API changes
in the stable branch. These changes create (a lot of) unexpected
work for everybody depending on Jackrabbit with their own projects. If
we do need API changes we have to branch off 2.10 first in a stable
maintenance
On 05/08/2015 17:58, Bart van der Schans wrote:
Hi guys,
I really have to agree with Unico here. We should not make API changes
in the stable branch. These changes create (a lot of) unexpected
work for everybody depending on Jackrabbit with their own projects. If
we do need API changes we
A candidate for the Jackrabbit 2.10.2 release is available at:
https://dist.apache.org/repos/dist/dev/jackrabbit/2.10.2/
The release candidate is a zip archive of the sources in:
https://svn.apache.org/repos/asf/jackrabbit/tags/2.10.2/
The SHA1 checksum of the archive is
28 matches
Mail list logo