On Fri, Jul 5, 2013 at 9:57 PM, David Mason wrote:
> OK, sounds good, but it would be great it someone who Has A Clue
> (unfortunately not me at this point) could go through those old
> tickets and clean them up - i.e. close them as fixed, duplicates, or
> will-not-implement. Call it project hyg
OK, sounds good, but it would be great it someone who Has A Clue
(unfortunately not me at this point) could go through those old
tickets and clean them up - i.e. close them as fixed, duplicates, or
will-not-implement. Call it project hygiene - make the project look a
lot more professional.
Should
On Fri, Jul 5, 2013 at 9:31 AM, Stephan Beal wrote:
> On Fri, Jul 5, 2013 at 5:49 AM, Matt Welland wrote:
>
>> You might want to scan through the open tickets looking for issues that
>> would impact your intended usage and then either test the latest fossil
>> against those issues or ask on the
On Fri, Jul 5, 2013 at 5:49 AM, Matt Welland wrote:
> You might want to scan through the open tickets looking for issues that
> would impact your intended usage and then either test the latest fossil
> against those issues or ask on the list specifically about it.
>
+1
We don't often tend to ti
Hi Dave,
As with any open source project YMMV but I've been very grateful for the
responsiveness of the fossil core team to important fixes.
Looking at the open ticket list I see that some of the tickets left are
controversial (for example one ticket is on whether or not an update should
bring ba
Hi, Just discovered fossil and it looks interesting on several fronts.
Currently using Mercurial.
The only thing that concerns me is the ticket list. There are open
Code_Defect tickets from 2009, and that doesn't give me a warm fuzzy
feeling. And after all, of your software toolkit, the part yo
6 matches
Mail list logo
