what about modules that have dependency on other modules. how can we specify which parent module version my module supports?<br><br><div><span class="gmail_quote">On 3/6/08, <b class="gmail_sendername">Nancy Wichmann</b> <<a href="mailto:nan_wich@bellsouth.net">nan_wich@bellsouth.net</a>> wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex">
> People with modules that never provide official releases cause more than a<br> bit of heartburn and<br> > confusion in the community. This change is one of many that attempts to<br> further penalize and<br><br>> marginalize projects that never create official releases.<br>
<br><br>I understand this, and largely agree with it. For the most part, I use -dev<br> as sort of an "alpha" state that doesn't remove the old official version.<br><br> Having now looked at it, I would really like to see the checkmark and red X<br>
taken off. I think the red X really makes more statement than should be<br> made here. The colors should be sufficient.<br><br> Nancy E. Wichmann, PMP<br><br><br></blockquote></div><br><br clear="all"><br>-- <br>Oleg Terenchuk <br>
Web Manager / Developer<br>Phone: 917 - 306 - 5653