Forums

Forget about my first answer below, I did not read the mail carefully
and answered as if
the core did not moved in his own folder.

Then, I am fine with the changes. Moving the extensions out of the trunk
or putting everything
under trunk, I don't mind.

As for the visibility for the modules, I am not sure that it will change
much, more visible and detailled
documentation will probably be required as well.

Cheers,
Nico


Le 02/03/2012 17:36, Nicolas Rodriguez a écrit :
> I would be -1 for the changes.
>
> Yes, modules and extensions, in theory, need to provide new versions
> when a new version of the jsbml core is out.
>
> But anyway, they can have a life on their own and making release
> independently of the core.
>
> A new minor version of the core might not need any changes in any of the
> modules or extensions.
> And modules and extensions can release new versions while the jsbml core
> does not change.
>
> So I will be more in favor of putting extensions out of the core/trunk
> than putting modules inside it.
>
> May be, modules and extensions version number/name could contain the
> version of jsbml core they are written for ?
> A bit like the SBML namespaces for SBML L3 packages need to contain the
> version of the SBML core they support ?
>
> Then each modules or extensions can make it's own tags and branches.
>
> Nico
>
>
> On 02/03/12 09:14, Andreas Dräger wrote:
>> Dear all,
>>
>> since the very beginning of the JSBML project, it is structured as follows:
>>
>> JSBML
>> |- trunk
>> |- modules
>> |- tags
>> |- branches
>>
>> Recently, within the trunk directory, we now have the sub-folder
>> extensions. I would now like to suggest to shift the modules folder also
>> into the trunk and to create a folder core there, leading to this structure:
>>
>> JSBML
>> |- trunk
>> |- core
>> |- extensions
>> |- modules
>> |- tags
>> |- branches
>>
>> This would significantly increase the visibility of the modules and
>> would also allow us to maintain all packages within the identical trunk.
>> When there is a new release of JSBML, users could be sure that all the
>> extension packages and all modules are compatible with the current core.
>>
>> Proposing this, I am looking forward to your opinions on this.
>>
>> Cheers
>> Andreas
>>
> ____________________________________________________________
> To manage your jsbml-development list subscription, visit
> https://utils.its.caltech.edu/mailman/listinfo/jsbml-development
>
> For a web interface to the jsbml-development mailing list, visit
> http://sbml.org/Forums/
>
> For questions or feedback about the jsbml-development list,
> contact sbml-team@caltech.edu

____________________________________________________________
To manage your jsbml-development list subscription, visit
https://utils.its.caltech.edu/mailman/listinfo/jsbml-development

For a web interface to the jsbml-development mailing list, visit
http://sbml.org/Forums/

For questions or feedback about the jsbml-development list,
contact sbml-team@caltech.edu