> > Hm, I'm not sure I understand what you mean. I understood the contents > of a release are controlled via TORELEASE. And we don't release files > which are under construction or being refactored. When format/print are > combined either give the combination (temporary) another name or wait > until it is stable.
That's it: a temporary name, or wait until stable. In a ideal world, one would create a temporary SVN branch, work on it for refactoring, then merge back to trunk. But... > > asty one, there could > > be other still unknown impacts. Your point on this ? > > Yes, we better wait for these being fixed. But not too long. Do we have > libraries which are candidate for the next release which need these fixes? Well it's only about jallib libraries, it's about what users can do with them. If we release right now, users have to use version 2.4j. If they want to pass pins as parameters, if something else related to these bugs, then they can't use last jallib's version. Cheers, Seb -- Sébastien Lelong http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
