[ckan-dev] Call for translations and testers for the upcoming CKAN 2.6 release

[Adrià Mercader]

Hi Rick,

Don't worry about cluttering the issues tracker (it is already
cluttered :). We have two weekly dev meetings where we triage all
incoming issues and we will assign labels or close issues as necessary
(yours probably will be marked as "Good for contribution"). I'd rather
have low priority issues reported than put people off from reporting
them.

We can definitely consider a priority based labelling system if that is useful.

Thanks for testing!

Adrià

On 18 October 2016 at 16:31, Rick Leir <rleir at leirtech.com> wrote:
> Hi Adrià and all,
> I am new here, so hi everyone. I did some testing at beta.ckan.org, and
> opened a minor github issue. There is no way to  mark it as minor, so it
> clutters the list of issues.  Would it make sense to label the issues
> according to priority? Maybe labels like MinorPri, MediumPri, HighPri. There
> are already labels 'Priority' and 'Medium' but they are not in use. And I do
> not have privileges to add labels, so would someone with such privilege
> please label my issue(s) at a lower pri? We might want to discuss triaging.
>
> What do you think of the Robin policy (link below) or the first answer at
> StackExchange (link below).
> Thanks
> Rick
>
> ref:
> http://programmers.stackexchange.com/questions/129714/how-to-manage-github-issues-for-priority-etc
> https://robinpowered.com/blog/best-practice-system-for-organizing-and-tagging-github-issues/
>
>
> On 2016-10-18 08:06 AM, Adrià Mercader wrote:
>>
>> Hi everybody,
>>
>> We have started the process of releasing the next CKAN version.
>>
>> If you speak a non-English language and want to help make CKAN
>> multilingual please update the translations on Transifex (you will
>> need a Transifex account, which takes 1 minute to set up). There are
>> only 20 new strings since last version so it shouldn't take much time
>> to get them updated!
>>
>> Make sure to translate on the 2-6 resource:
>>
>> https://www.transifex.com/okfn/ckan/2-6/
>>
>>
>>
>> Additionally, if you can help us test the beta release branch and
>> report any issue that would be great as well! You can:
>>
>> * Test the live http://beta.ckan.org/ instance, which is running the
>> release branch
>>
>> * Checkout locally the `dev-v2.6` branch
>>
>> * Install the beta deb packages on an Ubuntu VM:
>>
>> http://packaging.ckan.org/build/python-ckan_2.6.0b-precisebeta1_amd64.deb
>> http://packaging.ckan.org/build/python-ckan_2.6.0b-trustybeta1_amd64.deb
>>
>> Thanks!
>>
>> Adrià
>> _______________________________________________
>> ckan-dev mailing list
>> ckan-dev at lists.okfn.org
>> https://lists.okfn.org/mailman/listinfo/ckan-dev
>> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev