<quote who="Matt S Trout"> > Gavin Henry wrote: >> What's the trigger level of addition/fixes/docs needed to justify a new >> release by the way? Just interested. > > The general rule of thumb for update releases tends to be "one > showstopper" > (broken tutorial counting and triggering 003) or "accumulated enough minor > fixes to be worth it" (e.g. the assorted bits in 002).
Understood. > > This isn't hard and fast though, it's basically dependent on the judgement > of > the core team - we try and strike a balance between getting fixes out > there > and inflicting an update treadmill on the user base. > > -- > Matt S Trout Offering custom development, consultancy and > support > Technical Director contracts for Catalyst, DBIx::Class and BAST. > Contact > Shadowcat Systems Ltd. mst (at) shadowcatsystems.co.uk for more > information > > + Help us build a better perl ORM: > http://dbix-class.shadowcatsystems.co.uk/ + > > _______________________________________________ > List: [email protected] > Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst > Searchable archive: > http://www.mail-archive.com/[email protected]/ > Dev site: http://dev.catalyst.perl.org/ > _______________________________________________ List: [email protected] Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
