Opened 12 years ago

Closed 12 years ago

#573 closed Task (fixed)

Differences between svn tagged version and released version

Reported by: jean-mat grimaldi Owned by:
Priority: Normal Milestone:
Component: General Version:
Keywords: Cc:

Description

Hello Fred Alfonso and everybody,

I try to make things the more simple for FCKeditor.Plone package.

To make FCKeditor.Plone svn update more simple for users, i used somewhere in FCKeditor.Plone repository this "svn:externals" property : fckeditor_src http://svn.fckeditor.net/FCKeditor/tags/2.4.3

This allows users to get all things in one svn update (fckeditor + fckeditor.plone)

But it seems that svn 2.4.3 tagged version and fckeditor2.4.3 released version are not the same products.

I suppose it is because the svn version do not use the packaged javascripts. Of course it's a good thing for developpers, but don't you think that the "tagged" version must be exactly the same as the released version ? i think that tags and trunk could be different ...

Second question : what can i do to make fckeditor.plone release in this situation, without downloading the product from sourceforge (as i used to do before with a bad svn users's feed-back)?

Many thanks

Jean-mat

Change History (3)

comment:1 Changed 12 years ago by Frederico Caldeira Knabben

Hi Jean-Mat,

The version branches must reflect the "development version" of the release. The fact is that the "public version", has "less information" than the "development version". So we would lost things on making the opposite.

The solution for your svn:externals is to simply point to "FCKeditor/releases/stable" in the SVN. It is enough to specify the revision to get the "public version" you want. You can check the list of its revisions [log:FCKeditor/releases/stable here].

So, if you get revision 381, you get FCKeditor 2.4.3, while revision 242 brings you FCKeditor 2.4.2.

Does it means we can close this ticket?

I hope you are having success with the FCKeditor product and the Plone community.

Thanks again for your contributions.

PS.: We should have those kinds of discussions at our dev mailing list?. But it is ok, just because it's you :)

comment:2 Changed 12 years ago by jean-mat grimaldi

Hello Fred

The solution for your svn:externals is to simply point to "FCKeditor/releases/stable" in the SVN. It is enough to specify the revision to get the "public version" you want. You can check the list of its revisions here.

it's perfect !

Does it means we can close this ticket?

Yes of course

I hope you are having success with the FCKeditor product and the Plone community.

Yes many users like it and we don't need any advertising because FCKeditor is just a good product ;-)

We should have those kinds of discussions at our dev mailing list. But it is ok, just because it's you :)

I will subscribe to these lists with many pleasure.

Bye

Jean-mat

comment:3 Changed 12 years ago by Frederico Caldeira Knabben

Resolution: fixed
Status: newclosed

That's great! Thanks again Jean-mat.

Note: See TracTickets for help on using tickets.
© 2003 – 2019 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy