On 7/14/09 12:23 PM, David Savage wrote:
Ok, makes sense. I'll do that - I guess I have priviledges to set up
versions in the felix jira? I'll try and bounce back if I can't...
As an aside I was planning to try to build sigil with sigil vs via maven:
https://issues.apache.org/jira/browse/FELIX-
Ok, makes sense. I'll do that - I guess I have priviledges to set up
versions in the felix jira? I'll try and bounce back if I can't...
As an aside I was planning to try to build sigil with sigil vs via maven:
https://issues.apache.org/jira/browse/FELIX-1323
This would make it a good test scenar
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 bette
[
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. Wonderi
