Ok, how about if I put it this way: Does a tag make it more stable and/or complete than any individual commit? I don't think so. You don't have to make a RPM off HEAD, though. Every commit has a marker, and you can use that instead of a tag. On Arch Linux that I use, there are many packages like that, and they are no worse than whatever upstream tagged as an explicit release.
Point is, web.py's commits tend to be clean and frustration-free, at least as far as I can tell. Others may correct me on that. On Fri, Mar 19, 2010 at 7:51 PM, Gregg Lind <[email protected]> wrote: > Branko, > > Well, I beg to differ about there being no need. There may not be a > programmatic need, but there is a business need. My company prefers > to deploy via RPM, and making an RPM off HEAD is inelegant. Frequent > tagged versions (even if they aren't major releases) would help, and > they aren't that much cost (just make a git tag, and be done :) ). > > (As an aside, I'd be interested in helping beef up regression tests on > web.py) > > Gregg > > On Mar 19, 1:33 pm, Branko Vukelic <[email protected]> wrote: >> There's no need. I've never seen a commit to master branch break >> something. You can safely use the latest development version without >> too much problem. At some level, you could probably fix a bug >> yourself, or at least spot it, courtesy of small code base. >> >> >> >> On Fri, Mar 19, 2010 at 6:15 PM, Greg Milby <[email protected]> wrote: >> > the frequent releases would help functionality to be fully tested/gather >> > feedback to help shape future releases & like-functionality (jmho) >> >> > On Fri, Mar 19, 2010 at 12:24 PM, Gregg Lind <[email protected]> wrote: >> >> >> web.py is under active development. Perhaps it should have shorter >> >> release cycles (between versions), to make it easier for downstream >> >> users to get benefits, while still having properly packaged versions >> >> (0.33, 0.34)... >> >> >> We just spend this morning at my workplace arguing about whether to >> >> make an rpm of HEAD (calling it 0.33.1) or whether to just include >> >> the /web in our source tree. I'd like to not do that again :) >> >> >> Gregg >> >> >> -- >> >> You received this message because you are subscribed to the Google Groups >> >> "web.py" 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/webpy?hl=en. >> >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "web.py" 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/webpy?hl=en. >> >> -- >> Branko Vukelić >> >> http://foxbunny.tumblr.com/http://www.flickr.com/photos/16889...@n04/http://www.twitter.com/foxbunnyhttp://github.com/foxbunny > > -- > You received this message because you are subscribed to the Google Groups > "web.py" 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/webpy?hl=en. > > -- Branko Vukelić http://foxbunny.tumblr.com/ http://www.flickr.com/photos/16889...@n04/ http://www.twitter.com/foxbunny http://github.com/foxbunny -- You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en.
