On Tue, Apr 27, 2010 at 10:13 AM, Ramiro Morales wrote:
> Hi all,
>
> What do you guys think about organizing something like this? The goal
> and motivation help get the documentation contents as polished as
> possible for the 1.2 release.
>
> If things go as planned the 1.2 RC should have been al
On Mon, Apr 26, 2010 at 10:13 PM, Ramiro Morales wrote:
> Hi all,
>
> What do you guys think about organizing something like this? The goal
> and motivation help get the documentation contents as polished as
> possible for the 1.2 release.
>
> If things go as planned the 1.2 RC should have been al
Hi all,
What do you guys think about organizing something like this? The goal
and motivation help get the documentation contents as polished as
possible for the 1.2 release.
If things go as planned the 1.2 RC should have been already packaged by
then and we should be near the date of the tagging
Hi Ryan,
Moving discussion here off the Trac ticket.
On Apr 25, 5:44 pm, Ryan wrote:
> A decent workaround is for my post_delete hook to pass
> force_update=True and catch DatabaseError when saving the article, in
> case it has already been deleted. But I think it would be nice if
> django just
Just to make it clear I am not saying that Launchpad is "The Solution"
to all the problems. I have decided to dig in its documentation and
post the feature that I found interesting and I discover that
launchpad has grown a some very useful features with regards to the
issues we were discussing.
On
On 04/25/2010 05:15 PM, Russell Keith-Magee wrote:
However, the *huge* impediment that you have avoided mentioning is
that moving to Launchpad would require moving Django to using Bazaar
for version control. Moving to a DVCS has been proposed many times in
the past, and rejected. The reasons for
