Hi
> > Other projects have the concept of 'release candidates'. We could > mark the 'candidate' in the SVN database, and the 'JALLIB Team' would > have a chance to preview the 'candidate', before it is officially > release and announced. > jallib also has this concept, even if not named the same. As Rob explained, jallib 0.5 was available few weeks ago in group's file section for review. Between this beta (we call this like that) and the final release, we try to do a "feature freeze", which is also a concept used on other projects... A release isn't an instant process, even the packages building themself take quite a lot of time (it took me almost a whole day). You should have considered this release as started by this date few weeks ago, and you should have added your files by this time (and I think it would have been feasible since your last commits only shows "clean up for release" actually adding your fiwihex -- Eur, I guess -- sponsor in header as comments). We do this for every release, 0.5 is no exception. If you want to change things, good. Provide options and guidelines. Cheers, Seb -- 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.
