RT2 release planning;


#1

So as I mentioned a month or so ago, I’m going to be spending
the month of April travelling throughout japan with a backpack
and a railpass. I was really really really hoping to crank through
beta 2 and move onto a release candidate before I left the country.

Sadly, well, real life intervened. Some minor bugs cropped up.
I’ve spent a bit of time pursuing some consulting gigs so I can
make enough money to eat and keep a roof over my head while
I continue to work on free software for y’all.

So I’ve juggled the release plan a little bit. There’s now going
to be a ‘beta 3’ which contains some functionality and ‘cosmetic’ issues
and the RT1 importer.

beta 2 is stuff that I think I can get to before I leave. bugfixes will
have priority over features. and I’m likely to punt issues to beta 3
if I run out of time.

The goal is that beta 2 should be ready for limited deployment by folks
who are clueful or foolhardy. It’s at the point where I would personally
use it for a customer facing ticketing system. But, well, I fall into at least
one of the categories mentioned above (the latter). And I know the code
inside and out.

In my absence, it is my hope that folks will use rt-devel to help each other
get current betas running and to help find and fix bugs. I expect to
be able to check in at least once a week…but don’t be too surprised
if you don’t hear from me for most of the month.

    Jesse

jesse reed vincent – root@eruditorum.orgjesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

After all, it’s not every day you meet up with an evil power
-M. Bulgakov

Rt-announce mailing list
Rt-announce@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-announce


#2

In my absence, it is my hope that folks will use rt-devel to help each other
get current betas running and to help find and fix bugs.

Can anyone else check fixes into fsck.com CVS?

I expect to
be able to check in at least once a week…but don’t be too surprised
if you don’t hear from me for most of the month.

meow
_ivan


#3

In my absence, it is my hope that folks will use rt-devel to help each other
get current betas running and to help find and fix bugs.

Can anyone else check fixes into fsck.com CVS?

Not right now. The best procedure is to report bugs (and fixes)
to rt-2.0-bugs@fsck.com. (If you attach unified diffs as MIME attachments,
it’ll make my job easier )I’ll be checking in periodically.
Assuming I find reasonable net, I suspect that you’ll see a new release every
10-15 days.

Before I go, I’ll see about setting up a list the folks can subscribe
to in order to get ticket create / correspond messages for rt-2.0-bugs.

    -j

Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel

jesse reed vincent – root@eruditorum.orgjesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

pretty soon we’re going to HAVE to have hypertext mail!
–Tim Berners Lee. (8 Jan 1993 on www-talk)