wasn't able to follow your use-case exactly:
>
> On Monday, 10 December 2018 13:47:54 UTC+1, Ira Abbott wrote:
>>
>> We all learn very early in playing with django to set a site and a
>> SITE_ID. Once we operate as multiple sites, we either use the multiple
>> processes, eac
s to scale that will ultimately benefit the framework
as a whole.
On Monday, December 10, 2018 at 3:21:53 PM UTC-5, Ira Abbott wrote:
>
> FWIW: Please consider my contribution of $84 (one bulk JIRA license for
> one year) to be just that.
>
> On Monday, December 10, 2018 at 2:14:07 PM UTC
Hi,
Just in case that JIRA crack was NOT sarcasm ...
https://www.atlassian.com/software/jira/pricing How many users would be
needed? If going this way, I smell the need for a gateway / JIRA backend
for the community site and small number of actual JIRA users with the
creation coming from a
This project probably qualifies here:
https://www.atlassian.com/software/views/open-source-license-request
On Monday, December 10, 2018 at 2:05:40 PM UTC-5, Ira Abbott wrote:
>
> Hi,
>
> Just in case that JIRA crack was NOT sarcasm ...
>
> https://www.atlassian.com/software
FWIW: Please consider my contribution of $84 (one bulk JIRA license for one
year) to be just that.
On Monday, December 10, 2018 at 2:14:07 PM UTC-5, Zachary Garwood wrote:
>
> I'd pay money to NOT use Jira.
>
> On Mon, Dec 10, 2018, 11:09 AM Dan Davis
> wrote:
>
>> Tom, you are right about the
A few questions:
You are posting this example because you believe you have found a bug in
django, correct? Otherwise, please post to the users group.
The behavioral problem described is "exclude - no really exclude",
correct? You perform an exclusion and do not see the exclusion and then
I like this solution, as it applies the fix for new things moving forward
with no change in
behavior to cause problem for existing tweaked in sites. The most likely
time to run in to this problem is, in my opinion, is when varying platforms
or starting fresh
projects. Once settled in to a
We all learn very early in playing with django to set a site and a
SITE_ID. Once we operate as multiple sites, we either use the multiple
processes, each configured with a separate SITE_ID or we can now pass a
request in. However, I assume for backward compatibility, SITE_ID must be
Hi,
>From the perspective of someone who just joined the group, I am glad to see
that I was not alone not immediately finding the correct path or
participation. I am, however grateful that the community appears to have
the introspection and means of moving it forward.
Being new, I am curious
