Thanks, I'll comment out the entire RELEASE line. ie.
NB. RELEASE=: 'j601 j602'
until the code become stable. Incidentally package manager (server side) is
driven by this config file
http://www.jsoftware.com/jal/j601/addons.txt
to determine what version to be included in catalog repository so that a tag
branch in svn does not guarantee that version will appear in user's catalog window.
Sherlock, Ric wrote:
---bill lam wrote:
Sherlock, Ric wrote:
Would another option be to only commit your non-production
version to
J602 which is beta anyway? Once it is stable you could then
commit the
production version to J601 and J602.
Good idea but I don't know how to do it or will that be
supported by package manager.
To make an addon version only available in J602, I think you just need
to remove j601 from RELEASE in manifest.ijs.
So instead of:
RELEASE=: 'j601 j602'
VERSION=: '1.2.2'
You would use:
RELEASE=: 'j602'
VERSION=: '1.2.2'
Once you are ready to release 1.2.2 (or 1.2.3 etc) as production code
you would commit a manifest.ijs that includes both j601 and j602 again.
Again, I haven't used this at all so am just basing this on my reading
of http://www.jsoftware.com/jwiki/Addons/Versioning
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
--
regards,
bill
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
