I've been inspired to see if I could help at all - so I've submitted comments to a couple of tickets. Perhaps naively, I reckon they can just be patched into the source (by someone who knows how to do that - I have no chance!) and closed.

Tickets are:

843     Newline rendering in notes is scetchy.
https://www.assembla.com/spaces/tracks-tickets/tickets/843-newline-rendering-in-notes-is-scetchy-

898     Edit popup for actions goes away too quickly
https://www.assembla.com/spaces/tracks-tickets/tickets/898-edit-popup-for-actions-goes-away-too-quickly

Hope that's of some use!

--
Orlando.


On 02/04/2010 18:47, Eric Allen wrote:
I set a tentative date of April 30th for the 2.0 release when I re-named
1.8. How does that sound to everybody? Maybe we do the RC at the end of
April and release in May?

I just closed 10 tickets today and pushed a few more off to 2.1, so the
pile is looking really manageable. What else is blocking 2.0RC1?

On Mon, Mar 22, 2010 at 2:47 PM, Eric Allen <[email protected]
<mailto:[email protected]>> wrote:

    Well, we could do a 1.7.1 with just the last bug fix.
    Okay, that makes sense. If we could get download stats, that would
    be a great way of figuring out how many users are keeping up enough
    to see a minor release.

    I assume 2.0 still takes weeks to get ready for RC and some time
    for final
    Yeah, even with the reduced # of tickets, it's still going to take
    quite a bit of work, and I'm struggling to finish off my last
    semester of college, so yeah, interim releases are good.

    On Mar 22, 2010, at 11:09 AM, Reinier Balt wrote:

    Well, we could do a 1.7.1 with just the last bug fix. Close 1.7
    then and concentrate on 2.0. I assume 2.0 still takes weeks to get
    ready for RC and some time for final
    Reinier
    *Van:* Eric Allen [mailto:[email protected]
    <mailto:[email protected]>]
    *Verzonden:* maandag 22 maart 2010 15:03
    *Aan:* Reinier Balt
    *CC:* track-discuss
    *Onderwerp:* Re: [Tracks-discuss] Re: 2.0 release

    Awesome! Thanks for cleaning up the tickets. This makes 2.0 look a
    lot more manageable. Should we just move the remaining 1.7.1
    tickets over to 2.0, since we're giving up on that release?

    On Fri, Mar 19, 2010 at 9:32 AM, Reinier Balt <[email protected]
    <mailto:[email protected]>> wrote:
    For 1.7.1 I reduced the tickets to a few that are relevant and
    present in
    2.0 too, including one that makes your database inconsistent.
    I closed some of them because of your jQuery work, i.e. not fixing
    stuff
    that is fixed for 2.0.

    I removed myself from a lot of tickets so other can pick them up.
    I hope to
    fix some of the recurring todo tickets.

    Reinier

    -----Oorspronkelijk bericht-----
    Van: [email protected]
    <mailto:[email protected]>
    [mailto:[email protected]
    <mailto:[email protected]>] Namens Eric
    Allen
    Verzonden: zondag 14 maart 2010 22:18
    Aan: track-discuss

    Onderwerp: [Tracks-discuss] Re: 2.0 release

    I think before we even think about a pre-release, we need to
    whittle down
    the number of tickets to a reasonable level. Reinier, you have a
    ton of
    Accepted tickets. Do you want to push some of those off to 2.1,
    New, or
    assign them to me?

    As for 1.7.1, which of those tickets are still an issue in master?

    On Mar 8, 2010, at 4:20 AM, Reinier Balt wrote:

    > We could go for a pre-release which gives us some more testing of the
    > current development tree.
    > There is a 1.7.1 bug that is impacting 1.8 too. I think we could
    forget
    > about releasing 1.7.1
    > given the available time :-(
    >
    > I'll try to pick up some of the recurring stuff the coming days,
    but my
    > spare time is very much
    > fragmented lately.
    >
    > Reinier
    >
    > -----Oorspronkelijk bericht-----
    > Van: [email protected]
    <mailto:[email protected]>
    > [mailto:[email protected]
    <mailto:[email protected]>] Namens BSAG
    > Verzonden: zondag 7 maart 2010 15:52
    > Aan: Eric Allen
    > CC: track-discuss
    > Onderwerp: [Tracks-discuss] Re: 2.0 release
    >
    > On 07/03/2010 0:23, Eric Allen wrote:
    >> We really need to push out a new release of Tracks in the near
    future,
    >> here. Dependencies and the jQuery stuff seem to be pretty stable
    at this
    >> point, so I think we're close! The major outstanding issues seem
    to be
    >> surrounding recurring todos. Reinier, care to chime in? We have
    almost
    >> 50 open tickets on milestone 1.8 right now, so we need to start
    pushing
    >> things out. I'm not an admin on Assembla, so I can't create a 2.0
    >> milestone. Reinier or bsag, can you make me an admin so I can move
    >> things around for the release?
    >
    > I'm even more busy than ever, I'm afraid, so I'm not going to
    have much
    > time to help out :-(
    >
    > However, I have added you as an admin on Assembla, Eric, so you
    should
    > be able to move things around now.
    >
    > cheers,
    >
    > bsag
    >
    > --
    > but she's a girl - the weblog of a female geek
    > http://www.rousette.org.uk
    > [email protected] <mailto:[email protected]>
    > _______________________________________________
    > Tracks-discuss mailing list
    > [email protected]
    <mailto:[email protected]>
    > http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
    >

    _______________________________________________
    Tracks-discuss mailing list
    [email protected]
    <mailto:[email protected]>
    http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss





_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss


--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss

Reply via email to