SVN revision numbers

[hbf]

Dear list,

I am wondering if there is additional information for the ones among us that work with Alfresco SVN (instead of with fixed releases)? I've searched on the wiki and this forum but have found only outdated answers to the following answers:

1. Where is the SVN revision number of the current release(s) kept?

2. If I understand correctly, the Enterprise edition is a separate, initially nonpublic branch of a Community Edition; after some time, the changes are merged back to the Community Edition and the process starts again. Is this correct?

3. If so, where can I see the SVN revision number of a (already publicly available) Enterprise edition?

4. If I update my SVN code to a new revision, will the repository be updated automatically on restart? I understand that updates from official releases make sure that the repository data is correctly updated, but what about internal SVN revisions? I suppose they come without any update and we risk running into a situation where the repository cannot be down- nor updated, right?

Many thanks for answering,
Kaspar

[mikeh]

It's also in the release notes http://wiki.alfresco.com/wiki/Alfresco_Community_Edition_3.2r_Release_Notes

Mike

[mederic]

Thank you!
Mederic

[kevinr]

Now tagged in SVN as TAGS/V3.2.0-COMMUNITY-RM-FINAL

[gyro_gearless]

So what do you mean with "TAGGED"? As far as i can see, this information is not visible in the public SVN repository? The only thing i see is HEAD… I suppose it would be a big win if this tags were made in the public SVN, and it should only take a minute or two!

Just my thoughts
Gyro

[kevinr]

I have raised the public Tag visibility issue with our IT department.

Cheers,

Kev

[hr61369256]

Hi Kev,

… as I see, is the current Ubuntu 9.04/9.10  release of Alfresco-Community numbered with 3.2-9 (as the package is named in the synaptic list). Where can I find the corresponding svn revision number? (I only found those of 3.2 and 3.2r2).

And can I use the svn command as supposed to be used?
    svn co <url-to-alfresco-source-archive>[@<revision number>] … to check out a working copy of a certain revision number?

How does the database schema revisions correspond to the source code revisions? Or is it not relevant, because the source code generates or alters the schema as it should be?

Thanks a lot,
Ralf

[mrogers]

The database schema revision numbers identify which version of the database schema to use.      However a database schema may be used by several svn revisions.    

You can't determine anything about svn from the database schema number.

[hr61369256]

… sorry I'm not yet quite satisfied with your answer: so, my first question (revision numbers of the ubuntu community variant 3.2-9 which sounds different to 3.2 or 3.2r2) and the last question aboud the corresponding revision numbers (e.g.  sources of revision number 17663 correspond to database schema with revision number ????). Is there a own svn archive with all data base schemas?

For example when I install the ubuntu variant (july 2009) by pakhage system and later deploy the recompiled war-file of revision number 17663 (november 2009) , could there be a problem with missing database entities or something like that? Or does the war-file check the database schema and add/alter the missing ones?

thanks again, Ralf

[sandramokeeffe]

Hi,

I'm looking for the revision numbers of both 3.2r and 3.2r2.  I tried to retrieve them from the wiki, however I'm not sure if what is on the wiki is correct. 

I have the 3.2.0r version of Alfresco, and there is a difference between the source code I download from SVN (based on the revision from the wiki - 16803), and what was bundled with the download (from the network site).

For instance, begin method signature of the DeploymentReceiverService interface is different between the two.

I would appreciate any help in getting this resolved.

Thanks,
Sandra

[mrogers]

The wiki is correct.

However if you downloaded from the Network site then that's Enterprise 3.2, not community 3.2r and yes it s a different build and has a slightly different version of DeploymentReceiverService and is a different build.

However DeploymentReceiverService is not an API that I'd expect you to be programming against so as long as the versions match then there will be no problem.