So, when can we expect 2.0.1? Carl
On May 27, 5:24 pm, Mark Ramm <[email protected]> wrote: > > I too agree the accidental link should not be an issue....go ahead and > > make what we currently have RC2, do an official announcement. Then the > > things you referred to as "2.0.1" can go into the actual 2.0-final, > > with big fanfare and whatnot. 2.0-final is a big deal, and we'll > > probably get alot of new curious users coming to check out what > > TurboGears is all about for the first time because of it. Not having > > to release a 2.0.1 right off the bat gives a better impression as to > > TG's stability and security IMO > > Well, I respectfully disagree. 2.0.1 is not a big deal it fixes a > couple of very minor issues with non-standard setups, and if releasing > right away would cause trouble we can postpone it for a bit. > > But I think that a lot of people expect that we will be supporting the > release and fixing bugs, and a 2.0.1 release is not unlike the 1.0.1 > release that came out a few days after Django 1.0. As long as the > fixes are for minor issues, and are well documented I don't think that > having bugfix releases creates a bad impression -- in fact it tells > people that we care about the software and are commited to fixing > bugs. > > Besides all that I know some people who are eagerly awaiting a TG2 > final release in order to convince their bosses that this stuff is > ready for production use, and I care about those users and want to > help them out, and the potential marketing benifits of delaying the > release have to be weighed against their needs. > > --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
