Hi,
On Mon, Jan 18, 2010 at 4:44 PM, Jukka Zitting wrote:
> In fact I'd like to speed up the release schedule and cut the final
> release candidate already this week as soon as we've sorted out all
> the remaining Jira issues.
I'm just putting the finishing touches on the release and expect to
c
Hi,
On Wed, Jan 13, 2010 at 12:20 PM, Jukka Zitting wrote:
> I plan to cut one more Jackrabbit 2.0 beta today and (assuming no
> major issues) the final 2.0.0 release candidate two weeks from now on
> Jan 27th.
In fact I'd like to speed up the release schedule and cut the final
release candidate
Hi,
I plan to cut one more Jackrabbit 2.0 beta today and (assuming no
major issues) the final 2.0.0 release candidate two weeks from now on
Jan 27th.
BR,
Jukka Zitting
Hi,
On Wed, Dec 16, 2009 at 2:14 PM, Jukka Zitting wrote:
> I think we're ready to create the 2.0 branch and only apply bug fixes
> and other finishing touches there before the final release. More
> extensive changes should go into the branch only with a good enough
> reason why they should be in
Hi,
I think we're ready to create the 2.0 branch and only apply bug fixes
and other finishing touches there before the final release. More
extensive changes should go into the branch only with a good enough
reason why they should be included in 2.0 instead of 2.1.
I'll create the branch and cut a
Hi,
The connection pooling code is now in trunk and everything seems fine.
I'll cut a 2.0 beta4 release soon so we can push it out for more
testing as soon as possible.
As for the final 2.0 release, we still have the following blockers open:
[JCR-2195] Provide possibility to import protected i
Hi,
I wanted to do a 2.0-beta2 release two weeks ago at ApacheCon, but
even though I already cut the release candidate I never had time to
run the release vote. Now I'd like to get back on track by cutting
2.0-beta3.
We're getting closer to 2.0 final, but there still are blocker issues
to resolve
Hi,
I'll be doing another Jackrabbit 2.0 alpha tomorrow.
The JCR 2.0 API jar is now officially available from the JCP (see
[1]), and I'm hoping to get the jar uploaded to Maven central within a
few days. After that I would like to switch from the source-only alpha
releases we've been doing to a s
Hi,
On Wed, Sep 16, 2009 at 11:01 AM, Jukka Zitting wrote:
> I haven't yet looked in detail at all the open feature issues we have,
> but it would be really cool if we could have Jackrabbit 2.0 released
> by the ApacheCon US in early November. That would give us essentially
> one month time for a
Hi,
As David mentioned, JCR 2.0 is now approved and should become
available soon. This means that we are getting closer to being able to
release Jackrabbit 2.0. As another step on that way I'm doing another
alpha release today.
I haven't yet looked in detail at all the open feature issues we have
Hi,
We reached JCR 2.0 feature completeness with the alpha9 release, but
that's only part of the work to be done for the Jackrabbit 2.0
release. I'd now like to start focusing on the other aspects of the
release, so please set the Fix Version to 2.0.0 on any issues you
think should be fixed in the
On Tue, Aug 18, 2009 at 5:44 PM, Jukka Zitting wrote:
> Hi,
>
> On Wed, Aug 12, 2009 at 12:28 PM, Jukka Zitting
> wrote:
>> We're getting pretty close to feature-completeness... I'm planning to
>> cut a new alpha release (2.0-alpha8) tomorrow and will most likely do
>> another one (2.0-alpha9) nex
Hi,
On Wed, Aug 12, 2009 at 12:28 PM, Jukka Zitting wrote:
> We're getting pretty close to feature-completeness... I'm planning to
> cut a new alpha release (2.0-alpha8) tomorrow and will most likely do
> another one (2.0-alpha9) next week as we gear up towards the JSR 283
> final release.
We hav
Hi,
We're getting pretty close to feature-completeness... I'm planning to
cut a new alpha release (2.0-alpha8) tomorrow and will most likely do
another one (2.0-alpha9) next week as we gear up towards the JSR 283
final release.
BR,
Jukka Zitting
Hi,
There's another JCR 2.0 API jar version coming up (b113, see JCR-1104)
and I'm planning to do another alpha release (2.0-alpha7) once we have
those changes in trunk. I'm slightly optimistic that this might be the
last API change before the final JSR 283 release...
BR,
Jukka Zitting
Hi,
One more alpha before I head out for a two-week vacation: I'll update
the JCR API jar again tomorrow and cut a 2.0-alpha5 release candidate
based on that.
BR,
Jukka Zitting
Hi,
I'll probably cut a 2.0-alpha4 release soon as we've again seen good
progress in trunk.
BR,
Jukka Zitting
Hi,
Currently the data store doesn't work as expected (it was broken by a
recent change, probably adding support for the new Binary interface).
I like to fix that today.
Regards,
Thomas
On Tue, Jun 9, 2009 at 5:40 PM, Jukka Zitting wrote:
> Hi,
>
> Now that we've upgraded to a more recent versio
Hi,
Now that we've upgraded to a more recent version of the JCR 2.0 API
jar I'd like to do the second alpha release of Jackrabbit 2.0. The JSR
283 features are being ticked off one by one; the following have been
as resolved since alpha1:
[JCR-1564] JSR 283 namespace handling
[JCR-1589] JSR 2
Hi,
On Wed, May 20, 2009 at 10:52 AM, Jukka Zitting wrote:
> Now that the trunk is reasonably stable again, I'm planning to cut the
> first 2.0 milestone release next week.
As mentioned by Roy, we'd be better in line with the JCP terminology
if we used the term "alpha" for the milestone releases
Hi,
On Wed, May 20, 2009 at 11:56 AM, Torgeir Veimo wrote:
> 2009/5/20 Jukka Zitting :
>> I'm working on a migration tool (to be included already in Jackrabbit
>> 1.6) that will allow users to migrate content from one repository
>> configuration to another.
>
> Very good. With versioning and UUID
2009/5/20 Jukka Zitting :
> I'm working on a migration tool (to be included already in Jackrabbit
> 1.6) that will allow users to migrate content from one repository
> configuration to another.
Very good. With versioning and UUIDs intact I presume?
--
-Tor
Hi,
On Wed, May 20, 2009 at 11:23 AM, Torgeir Veimo wrote:
> 2009/5/20 Jukka Zitting :
>> Now that the trunk is reasonably stable again, I'm planning to cut the
>> first 2.0 milestone release next week.
>
> Will a 1.5 repository be two-way binary compatible with a 2.0 repository?
Not necessarily
2009/5/20 Jukka Zitting :
> Now that the trunk is reasonably stable again, I'm planning to cut the
> first 2.0 milestone release next week.
Will a 1.5 repository be two-way binary compatible with a 2.0 repository?
--
-Tor
Hi,
On Wed, Apr 29, 2009 at 11:13 AM, Jukka Zitting wrote:
> I'm also planning to set up a series of time-based milestone releases
> leading up to 2.0.0. Every few weeks I'd cut a new 2.0-M? release
> based on the then-current trunk. These milestones (essentially alpha
> releases) would allow peo
Hi,
On Tue, Apr 21, 2009 at 5:39 PM, Jukka Zitting wrote:
> Once the 1.x branch has been created on April 30th, we will upgrade
> the JCR dependency in trunk to the JCR 2.0 jar included in the JSR
> 283 proposed final draft.
I will start the migration tomorrow afternoon once 1.x has been
branch
Jukka Zitting wrote:
Hi,
As a followup to the Jackrabbit 1.6 release plan I sent earlier,
here's a quick roadmap towards Jackrabbit 2.0.
...
+1 on the specific plan, and also thanks a lot for doing the planning work!
BR, Julian
Hi,
As a followup to the Jackrabbit 1.6 release plan I sent earlier,
here's a quick roadmap towards Jackrabbit 2.0.
Once the 1.x branch has been created on April 30th, we will upgrade
the JCR dependency in trunk to the JCR 2.0 jar included in the JSR
283 proposed final draft. This will replace a
28 matches
Mail list logo
