I'm not really on anyone's side here, but I have two suggestions: 1. Maybe a simple vote will do, if enough people agree to release, it gets released. In this case, I think most agreed but there was no vote. 2. Release again with jallib 0.5.1 if major bugs are found in the official release, or if someone has a large issue with the release. This way the team can make an exception if there is a problem like this one.
The main thing is that everyone is happy, and as stated, that not too much work is involved. If a 0.5.1 was created for William, would it make anyone upset? Would it be too much work? I believe William is a great asset to jallib and could be considered for an exception. I may find a large bug in one of my libs someday that is within an official release, how do I fix it? If a major bug is not fixed, someone out there will say "hey, don't use the new jallib package, it has bugs". We'll have bugs like Microsoft that take a year to get fixed. I think the main issue was that someone said "lets release today", and one person said "ok" and it was done. Some time is needed for someone to raise a hand. Instead of "lets release today", we should say "lets release at the end of the week". Seb, Why does it take an entire day to make the release package? The bee package is done every Sunday, does it take you all day every Sunday? Can it be more automated? 2.4m was considered fully tested by the creator, that is good enough for me. My libs are fully tested by me (except for fat32 which I noted beta), do you trust my libs enough to have them in the official release? Matt. -- 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.
