Hi All, I vote for the inclusion of the fix.
On Sun, Nov 7, 2010 at 9:04 PM, Phillip Heller <[email protected]> wrote: > Inline... > > On Nov 7, 2010, at 9:51 AM, Mathias Behrle wrote: > > <snip> > > > Err. Release is the official announcement, not the upload of some > packages. > > > >>> Since 1.8 is not yet officialy released I agree to include it. > >> > >> That is ... eh, nonsense. If tagging, branching, > > > > Tagging and branching never ever constitute an *official* release. If you > don't > > wait for the official announcement, it is at your risk to use those > packages > > and be left with uninstallable situations. What do you want to do with > module > > account 1.8, if trytond 1.8 is missing? > > > >> to pypi doesn't constitute releasing 'officially' you've spent too much > >> time chatting to your marketing department. > > > > See above. > > The problem, though, is that pypi advertises availability. One can > subscribe to pypi's feed on twitter, for example, to be notified of new > packages. > > And, while the tryton project might make official announcements regarding > new releases, not all pypi packagers do that -- so if pypi is an official > channel of release, we cannot expect users to wait for a news announcement > (on a list to which they might not subscribe) to consider this release > "available". > > That said, I do feel this bug fix is worthy of inclusion, considering that > Neso's usefulness is severely impacted without it. > > Whether it's 1.8.0 or 1.8.1 is really inconsequential. What matters is > that the bug was identified and fixed. > > --phil -- Sharoon Thomas Business Analyst & Open Source ERP Consultant CEO @ http://openlabs.co.in -- [email protected] mailing list
