Hello baba,

Le 15 févr. 2006 à 02:36, BABA Yoshihiko a écrit :

Michèle

2006/2/11, Michèle Garoche <[EMAIL PROTECTED]>:
As there is a chill in Fink trees, I've put  there:

<http://cvs.sourceforge.net/viewcvs.py/fink/experimental/michga/>

new info file for bluefish-unstable:

bluefish-unstable.info (should be revision 1.1 on the site)

It is the future of bluefish. If you want to influence or participate
in its future, this is the best choice.

It can be installed concurrently with the normal version of bluefish
(whichever variant) without any conflict.

The info file is meant to work on 10.4-transitional unstable.

It should be available within a few hours.


I've heard that you can put a new revision/version if there is already in 10.4 tree, but make sure the revision number in 10.4 starts at 1001. In your case, bluefish is already in 10.4, so you can commit there.
That is not that simple. 

First it would be better to first push bluefish 1.0.5 in 10.3, 10.4-transitional, and eventually 10.4 all unstable branches. To do that, it would be nice to push bluefish 1.0.4 into 10.3, 10.4-transitional, and eventually 10.4 all stable branches (not sure it is possible, there may be possible missing dependencies at a given revision).
 
Then bluefish-unstable is really meant to always be a prewichever version package. That is it will never have a non pre version.  

When a given feature is considered as sufficently stable to get into the normal bluefish package, it gets into it after thorough testing on whichever systems are involved in bluefish development, that is a good representation of what currently exists.

If this complies with the chill, I'll be happy to put bluefish 1.0.4 in stable branches, 1.0.5 in unstable ones, and bluefish-unstable only in 10.4-transitional unstable at the moment (or maybe in other trees if people can test it on them).

Attachment: 36C471DED4B09EEB30A0281F2608DB2FE6F9E147.gpgkey
Description: Binary data


Reply via email to