Typically, we have trunk working on an odd numbered minor release as the
development version and then release an even numbered version. So,
perhaps Sigil should be 0.9.0-SNAPSHOT in trunk, working toward 1.0.0
(or 0.10.0 or whatever even number you want). This approach makes like a
little better with Maven and OSGi since 1.0.0-SNAPSHOT is less than
1.0.0 in Maven, but not in OSGi.
-> richard
On 7/14/09 12:03 PM, David Savage (JIRA) wrote:
[
https://issues.apache.org/jira/browse/FELIX-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Savage resolved FELIX-1326.
---------------------------------
Resolution: Fixed
relevant patches applied to svn.
Not currently targetted at a release. Wondering what this should be? I guess
current effort is to head towards a 1.0 of sigil on felix?
Refactor package names in code to org.apache.felix.sigil
--------------------------------------------------------
Key: FELIX-1326
URL: https://issues.apache.org/jira/browse/FELIX-1326
Project: Felix
Issue Type: Task
Components: Sigil
Reporter: David Savage
Assignee: David Savage
Priority: Critical
currently package names are org.cauldron.*
