hi
another option I'm considering while dealing with Jaluino packaging:
having more than one TORELEASE file, one being chosen by buildbot
according to some configuration done within its guts. So one would
include beta samples & libs, another only stable's. this would also
mean (probably) two different "compiler" directories. packaging
scripts would need updates, and I would need a lot of time that i'm
running out ;)
suggestions ?
cheers
seb
--
Sébastien Lelong
Le 28 févr. 2010 à 11:45, Joep Suijs <[email protected]> a écrit :
Hi guys,
2010/2/28 Rob Hamerling <[email protected]>
I agree we should not put beta-software in our official releases,
but I
don;t see problems with putting a beta-compiler in the 'bee'-
package.
This is what confused me (with commited new compiler as a result), I
did not concider bee-package as official release.
I always use the svn compiler, so won't test a beta compiler if it
is not there.
@seb
(we want to release some libs/samples not dependent to beta,
but compiler is still beta), how will we deal with that ?
How likely is it we do an official release when the compiler is
still in beta?
And if it is required, we can downgrade.
Joep
--
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
.
--
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.
