[Cherokee-dev] Issue 1397 in cherokee: +++ PLEASE READ – ISSUES ARE MOVING TO GITHUB – PLEASE READ +++

[cher...@googlecode.com]

Status: New
Owner: ----

New issue 1397 by psaod8fz...@gmail.com: +++ PLEASE READ – ISSUES ARE
MOVING TO GITHUB – PLEASE READ +++
http://code.google.com/p/cherokee/issues/detail?id=1397

In the next couple of days we are moving the issues to Github.


***************************************************************
* *
* If you found a bug, please leave open an issue at: *
* https://github.com/cherokee/webserver/issues *
* *
* Please do NOT create new issues in this issue tracker *
* *
***************************************************************

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherok...@lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

[Jeremy Morton]

Why move to Github and not Bitbucket? Could someone give a list of the
considerations? In my experience Bitbucket staff are more responsive to
development requests (network graph notwithstanding) and Bitbucket has a
nicer wide suite of tools to help with eg. Agile development.

--
Best regards,
Jeremy Morton (Jez)

On 19/03/2013 16:06, cher...@googlecode.com wrote:
> Status: New
> Owner: ----
>
> New issue 1397 by psaod8fz...@gmail.com: +++ PLEASE READ – ISSUES ARE
> MOVING TO GITHUB – PLEASE READ +++
> http://code.google.com/p/cherokee/issues/detail?id=1397
>
> In the next couple of days we are moving the issues to Github.
>
>
> ***************************************************************
> * *
> * If you found a bug, please leave open an issue at: *
> * https://github.com/cherokee/webserver/issues *
> * *
> * Please do NOT create new issues in this issue tracker *
> * *
> ***************************************************************
>

[- -]

I just read a blog post and thought that might be the alternative solution to migrate all issues into the webserver issues:
https://github.com/blog/1439-closing-issues-across-repositories

I also thought about omitting invalids and duplicates.

any thoughts?

---

Von: "cher...@googlecode.com" <cher...@googlecode.com>
An: cherok...@cherokee-project.com
Gesendet: 17:06 Dienstag, 19.März 2013
Betreff: [Cherokee-dev] Issue 1397 in cherokee: +++ PLEASE READ – ISSUES ARE MOVING TO GITHUB – PLEASE READ +++

Status: New
Owner: ----

New issue 1397 by psaod8fz...@gmail.com: +++ PLEASE READ – ISSUES ARE MOVING TO GITHUB  – PLEASE READ +++
http://code.google.com/p/cherokee/issues/detail?id=1397

In the next couple of days we are moving the issues to Github.


    ***************************************************************
    *                                                            *
    *    If you found a bug, please leave open an issue at:      *
    *        https://github.com/cherokee/webserver/issues        *
    *                                                            *
    *    Please do NOT create new issues in this issue tracker    *
    *                                                            *
    ***************************************************************

--You received this message because this project is configured to send all issue notifications to this address.

[cher...@googlecode.com]

Comment #1 on issue 1397 by psaod8fz...@gmail.com: +++ PLEASE READ – ISSUES

ARE MOVING TO GITHUB – PLEASE READ +++
http://code.google.com/p/cherokee/issues/detail?id=1397

Finished and working.
Some minor display bugs, but that's ok. There is still the original issue,
to have a look at, if there are doubts.