Waiting for a new compiler usually delays release for 3 or 4 weeks. I don't have issue with this, but I'm not sure it would worth it. Is there any "deal breaker" bugs in current release ? As for beta compiler could automatically be part of jallib dev (including jallib week builds).
Cheers Seb On 16 February 2013 11:12, Oliver Seitz <[email protected]> wrote: > Has anyone news from Kyle? He was working at a whole bunch of bugfixes > recently. Perhaps a new compiler beta could go in the beta release? > > Greets, > Kiste > > > Hi guys, > > Shall we release this WE ? I could force a weekly build tomorrow, we would > then consider it a beta, we check, and if ok, I'll produce final package ? > > Let me know > Cheers > Seb > > > On 6 February 2013 09:39, Rob Hamerling <[email protected]> wrote: > > > Hello Mike, > > > On 6-02-13 03:10, Mike K wrote: > > > So if I make a file change I should add it to both CHANGELOG and TORELEASE? > > > Yes, maintenance of CHANGELOG and TORELEASE is the responsibility of every > committer. > > When you change a library 'significantly' you should update CHANGELOG. > That may be a bug fix, a change of comments in your source which means a > change in the generated documentation, a new library, or anything else that > may have influence on programs or program development and is useful to > remember (think of someone else who needs or wants to change your library). > > You can commit a new library anytime, and then people can download and use > it. It needs not be fully tested, can even be experimental. > But it won't become part of a Jallib release package until after it has > been added to TORELEASE. So you need to update TORELEASE when you consider > your new library good enough for use by other people (or when you withdraw > a library for some reason of course). > > > > Regards, Rob. > > -- > R. Hamerling, Netherlands --- http://www.robh.nl > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to > jallib+unsubscribe@**googlegroups.com<jallib%[email protected]> > . > To post to this group, send email to [email protected]. > Visit this group at > http://groups.google.com/**group/jallib?hl=en<http://groups.google.com/group/jallib?hl=en> > . > For more options, visit > https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> > . > > > > > > -- > Sébastien Lelong > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/jallib?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/jallib?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Sébastien Lelong -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/jallib?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
