versioning implementation

[ChadDavis <ch...@gmail.com>]

I'm remoting with the davex/spi stack, Jackrabbit 2.0.0.

I'm would like to know what the current state of versioning
implementation is?  Is is mostly done? Partially done?

A list of major unfinished pieces would be helpful.

Thank you.

Re: versioning implementation

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Wed, Mar 17, 2010 at 5:30 PM, ChadDavis <ch...@gmail.com> wrote:
> When is 2.1 expected?

Probably in early April.

BR,

Jukka Zitting

Re: versioning implementation

[ChadDavis <ch...@gmail.com>]

Thanks Angela!

> jackrabbit 2.1.0 will be the first version were we run
> the complete tck-tests and jcr2spi-tests on the setup
> jcr2spi - spi2davex - jcrserver.

When is 2.1 expected?

I will probably be in a position to assist, but I need to get a bit
more up to speed on the Jackrabbit internals.

Re: versioning implementation

[ChadDavis <ch...@gmail.com>]

> See the 2.1 branch for the latest status of the code that's going to
> go into the 2.1 release.
>

Forgive me if these questions are dumb.  I want to understand the
branch, release and trunk nomenclature.

In particular, what are the differences between the 2.1 branch and the
trunk.  2.1 hasn't been formally released, correct?  So, is the 2.1
branch used to chunk off a line of stable code from the trunk so it
can be tested and fixed prior to a tagged release?

Re: versioning implementation

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Thu, Apr 8, 2010 at 9:14 PM, ChadDavis <ch...@gmail.com> wrote:
> I see this list in the trunk - 2.2-SNAPSHOT version of
> jackrabbit-spi2dav/pom.xm.  Are the issues listed in that document to
> be fixed in the 2.1 release, or the 2.2?

See the 2.1 branch for the latest status of the code that's going to
go into the 2.1 release.

BR,

Jukka Zitting

Re: versioning implementation

[ChadDavis <ch...@gmail.com>]

On Wed, Mar 17, 2010 at 10:26 AM, Angela Schreiber <an...@day.com> wrote:
> ChadDavis wrote:
>>
>> I'm remoting with the davex/spi stack, Jackrabbit 2.0.0.
>>
>> I'm would like to know what the current state of versioning
>> implementation is?  Is is mostly done? Partially done?
>
> jackrabbit 2.1.0 will be the first version were we run
> the complete tck-tests and jcr2spi-tests on the setup
> jcr2spi - spi2davex - jcrserver.
>
> the list of known issues for 2.1.0 can be found in
> the jackrabbit-spi2dav/pom.xml

I see this list in the trunk - 2.2-SNAPSHOT version of
jackrabbit-spi2dav/pom.xm.  Are the issues listed in that document to
be fixed in the 2.1 release, or the 2.2?

Re: versioning implementation

[Angela Schreiber <an...@day.com>]

ChadDavis wrote:
> I'm remoting with the davex/spi stack, Jackrabbit 2.0.0.
> 
> I'm would like to know what the current state of versioning
> implementation is?  Is is mostly done? Partially done?

jackrabbit 2.1.0 will be the first version were we run
the complete tck-tests and jcr2spi-tests on the setup
jcr2spi - spi2davex - jcrserver.

the list of known issues for 2.1.0 can be found in
the jackrabbit-spi2dav/pom.xml

for previous versinons there is no such list.
but you can query JIRA for issues fixed in spi2dav
for 2.1.0. that will give you an idea what was
broken in 2.0.0.

> A list of major unfinished pieces would be helpful.

-> JIRA.

regards
angela