1) It would be good to declare support for Django 1.2 and 1.3 I am not sure if that support should be complete due to currently complicated and relative not so important issues #1331/#1347 (static files new in Django 1.3) but one day it would require a backward incompatible change in Satchmo which will be best joined with a visible release name change to a new Beta.
2) New installation is relative easy but an upgrade can be complicated due to needed first "entrain" to South migrations and to individually experiment where to start it or to reminisce the history of the store. It requires at least a good manual. E.g. "If you see the column XY_something_new in the database, skip the first migration. If you see... skip the second migration." Otherwise the users get many database errors or forget to do some migrations or both. Hmm. I'm much slower than I ever earlier thought. I do not repeat that I am working on many things which are almost done... Do it to can have a nice Christmas :-) -- Hynek On 3 pro, 23:26, Chris Moffitt <[email protected]> wrote: > I feel like we need to get a new version of Satchmo tested and released. > I'm not aware of any show stopper bugs at the moment and feel pretty good > about the code at this time. > > What I'm proposing is tagging a Beta version and hoping people will do some > good testing on it. After a couple of weeks we'll track and only do bug > fixes, doc updates and translations. I would be ecstatic if we could get a > release out before Christmas. > > Anyone have any concerns with this timeline? > > Thanks, > Chris -- You received this message because you are subscribed to the Google Groups "Satchmo users" 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/satchmo-users?hl=en.
