Dear hakkers, since earlier today we have migrated our issue tracking off of Assembla and are now using GitHub Issues. We have had them enabled for quite a while in order to use labels for pull request validation, which created some confusion as to where to open tickets. Since Assembla is now read-only and referring to GitHub, this should not be an issue any longer. The other reason for the switch is that close integration between pull requests and issues did not work in the way we wanted it to on Assembla.
The GitHub staff was extremely helpful in fixing up my broken JSON export and ingesting it, thanks a lot! For the curious, you can find my Perl&XSLT project here. All imported tickets have the “imported” label and their description begins which a link to the old ticket in assembla; their ticket numbers match the assembla number plus 10,000, and we bumped the ticket counter to 15,000 for new tickets on GitHub. The process for tickets goes roughly like the following: someone creates a ticket without label or milestone one of the committers puts the “triaged” label on it and assigns a milestone eventually someone assigns themselves to the ticket and starts working, producing a pull request which mentions the number (as per our guidelines) after review and PR validation it gets merged and the ticket closed Happy hakking, Dr. Roland Kuhn Akka Tech Lead Typesafe – Reactive apps on the JVM. twitter: @rolandkuhn -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
