Hi Brian, I think that this option would be OK with us as well and we will try to get a release out early next week. But before we do could you please test this branch out to make sure that everything that you expected is still working ok. Then when you can give us the go-ahead we can then build and release.
Thanks, Prasith Brian Zentis wrote: > Kyle, > > My vote would be for #2. That would be a final good release with JDK > 5 which should be stable and all features working. That way if we > move to JDK 6 with no hiccups: super! But if there is a problem, we > have a working version to run our class from. > > Brian > > Kyle wrote: >> Brian, >> >> Just wanted to let you know that Matt and I have squished out the last >> bug (we hope) out of the Alien reader and we tagged the release in our >> svn. This means that we can continue with the development on the trunk >> and continue to move it over to use JDK 6. The only question now is how >> do we want to handle getting changes to you. As I see it we have three >> options: >> >> 1) We can build a release and just send it to you guys. >> 2) We can build a release and make it an official 'bug change' release >> 3) We can show you guys how to build a release using eclipse. >> >> I would just like input from Penn St. and also from Prasith as to what >> we should do. >> >> Thanks, >> Kyle >> >> >> >> > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Rifidi-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rifidi-developers
