Re: [Trac-dev] Roadmap to Trac 1.2
On Wed, Jan 21, 2015 at 9:54 AM, Greg Troxel g...@ir.bbn.com wrote: Ryan Ollos rjol...@gmail.com writes: Change of scheme to store numbers as numbers, rather than as strings, and generally to thereby use database consistency checking. There are many columns in the database that store values as int and int64. Do you have some specific fields in mind? http://trac.edgewall.org/browser/trunk/trac/db_default.py I think I really meant ticket_custom, which loses type safety for pretty much everything that isn't a string. It looks like #10040 has a patch for the behavior you are requesting: http://trac.edgewall.org/ticket/10040 -- You received this message because you are subscribed to the Google Groups Trac Development group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
Re: [Trac-dev] Roadmap to Trac 1.2
On Wed, Jan 21, 2015 at 5:35 AM, Christopher Nelson chris.nelson.1...@gmail.com wrote: ... In addition to the tickets currently assigned to 1.0.4 and 1.1.4, there are a few key features that I'd like to implement for 1.2: - #11469: Custom field admin panel - #1233: Components and Versions become first-class objects in the TicketSystem with their own Roadmap-like pages, TracLinks, macros, permissions, ... - #3098: Repository README rendering Some other features that have been worked and look promising for inclusion in the release are: - PyGit2 plugin - #8172: Plugin db upgrade infrastructure - #10672: Automatically minify Javascript and CSS - #11676: Reusable commenting module What do others have in mind to include in the release? The question isn't only for current committers, but I'm hoping to hear from people that would be willing to step up and implement the changes as opposed to please include feature X. http://trac.edgewall.org/ticket/10983 is important to me. If the patch needs rework, I'd be happy to do that. Thanks, I'll take a look in a few days and follow-up in the ticket if it looks like there are any issues remaining with the patch. -- You received this message because you are subscribed to the Google Groups Trac Development group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
Re: [Trac-dev] Roadmap to Trac 1.2
Ryan Ollos rjol...@gmail.com writes: Change of scheme to store numbers as numbers, rather than as strings, and generally to thereby use database consistency checking. There are many columns in the database that store values as int and int64. Do you have some specific fields in mind? http://trac.edgewall.org/browser/trunk/trac/db_default.py I think I really meant ticket_custom, which loses type safety for pretty much everything that isn't a string. -- You received this message because you are subscribed to the Google Groups Trac Development group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout. pgpnHMbgU_TYE.pgp Description: PGP signature
Re: [Trac-dev] Roadmap to Trac 1.2
On Wed, Jan 21, 2015 at 7:17 AM, Greg Troxel g...@ir.bbn.com wrote: Ryan Ollos rjol...@gmail.com writes: It seems like a good time to discuss what we plan to deliver for Trac 1.2, and when we will deliver it. So far I see one big feature, and some components that have been significantly improved: The two things that I'd like to see long term (separate from what should be in 1.2 or when there will be code) are: Integration of ticket dependencies into the base; this seems too fundamental to make optional. There are two kinds of dependencies: one is parent/child for hierarchical WBS (for task/enhancement tickets), and the other is blocking (for those, or for defects). With mastertickets you can one or the other, or have it be a little confused and do both. That is one of the features I have in mind for development in 1.3.x. The BloodhoundRelationsPlugin looks promising for backporting into Trac. http://trac.edgewall.org/ticket/31#comment:180 Change of scheme to store numbers as numbers, rather than as strings, and generally to thereby use database consistency checking. Looking forward to 1.2, is it too early to think about dropping support for Python 2.6 and support Python 2.7 and 3.3+ from a single codebase? As we get close to releasing 1.2 I'll raise another thread to talk about what features we have in mind for development in the 1.3.x line. From the pkgsrc viewpoint, dropping 2.6 is fine, as 2.6 is getting pretty crufty. -- You received this message because you are subscribed to the Google Groups Trac Development group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
Re: [Trac-dev] Roadmap to Trac 1.2
On Wed, Jan 21, 2015 at 10:17 AM, Greg Troxel g...@ir.bbn.com wrote: The two things that I'd like to see long term (separate from what should be in 1.2 or when there will be code) are: Integration of ticket dependencies into the base; this seems too fundamental to make optional. There are two kinds of dependencies: one is parent/child for hierarchical WBS (for task/enhancement tickets), and the other is blocking (for those, or for defects). With mastertickets you can one or the other, or have it be a little confused and do both. ... We use MasterTickets for blocking and Subtickets for WBS. It works quite well for us. Though I agree core support would be preferable. -- You received this message because you are subscribed to the Google Groups Trac Development group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
[Trac-dev] Re: Roadmap to Trac 1.2
Am Mittwoch, 21. Januar 2015 08:00:32 UTC+1 schrieb RjOllos: What do others have in mind to include in the release? The question isn't only for current committers I'd like to see the ticket field project as standard field. This would make it much easier for the multiproject plugin to integrate. I cannot promise to implement that plugin code for the Trac core due a big lack of time and knowledge about the core. But doing so would a huge pro to push Trac as alternative to Redmine and all those tools. Furthermore, I recommend to drop the idea of combining several Trac instances to a Meta-Trac in favour to the SingleEnvironment approach which fits the need of 95% of all users. CU, F@lk -- You received this message because you are subscribed to the Google Groups Trac Development group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
Re: [Trac-dev] Roadmap to Trac 1.2
... In addition to the tickets currently assigned to 1.0.4 and 1.1.4, there are a few key features that I'd like to implement for 1.2: - #11469: Custom field admin panel - #1233: Components and Versions become first-class objects in the TicketSystem with their own Roadmap-like pages, TracLinks, macros, permissions, ... - #3098: Repository README rendering Some other features that have been worked and look promising for inclusion in the release are: - PyGit2 plugin - #8172: Plugin db upgrade infrastructure - #10672: Automatically minify Javascript and CSS - #11676: Reusable commenting module What do others have in mind to include in the release? The question isn't only for current committers, but I'm hoping to hear from people that would be willing to step up and implement the changes as opposed to please include feature X. http://trac.edgewall.org/ticket/10983 is important to me. If the patch needs rework, I'd be happy to do that. ... -- You received this message because you are subscribed to the Google Groups Trac Development group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
Re: [Trac-dev] Roadmap to Trac 1.2
Ryan Ollos rjol...@gmail.com writes: It seems like a good time to discuss what we plan to deliver for Trac 1.2, and when we will deliver it. So far I see one big feature, and some components that have been significantly improved: The two things that I'd like to see long term (separate from what should be in 1.2 or when there will be code) are: Integration of ticket dependencies into the base; this seems too fundamental to make optional. There are two kinds of dependencies: one is parent/child for hierarchical WBS (for task/enhancement tickets), and the other is blocking (for those, or for defects). With mastertickets you can one or the other, or have it be a little confused and do both. Change of scheme to store numbers as numbers, rather than as strings, and generally to thereby use database consistency checking. Looking forward to 1.2, is it too early to think about dropping support for Python 2.6 and support Python 2.7 and 3.3+ from a single codebase? As we get close to releasing 1.2 I'll raise another thread to talk about what features we have in mind for development in the 1.3.x line. From the pkgsrc viewpoint, dropping 2.6 is fine, as 2.6 is getting pretty crufty. -- You received this message because you are subscribed to the Google Groups Trac Development group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout. pgpgp8KKpxAv0.pgp Description: PGP signature
