Hi, Marc. It's been a while since I've heard from you. I cannot ignore this recent uptick in interest in improving SJ. Timo just started working on these GUI improvement and I could not be happier about it. And at the same time Brian Allen is at work on the long-awaited Eclipse plugin. Let's all give Brian a hard time until the plugin is finished!
And now Marc wants to get into the game. Well, it certainly is past time for a new release cycle. The thing is, I remain very busy. But I've balanced SJ with other personal projects before, so I should be able to do it again. And this time, it looks like I won't be coding it all by my lonesome self. So let's do it! I don't want to set up an issues tracking system, so if someone wants to take the lead on that, you have my blessing. Same with a wiki. I can give someone shell access to the sourcejammer.org space on SF if we can host these things there. Other than that, let's put together a list of top priorities and a plan. Timo is making the client changes in the 2.1 branch. Long ago I started a 2.1.1 branch and made some major architectural changes to the client. I should take a look at that and see if it's in good enough shape to merge Timo's changes in or if the whole thing needs to be scrapped. I've kind of got a bad feeling about that branch because I left it partway done and largely untested, so I'm kind of afraid to even look at it. Here are my major hopes for a new SJ release cycle: 1) More integration with IDEs. Brian is working on Eclipse. I'm thinking of taking a look at JEdit. 2) Generate activity reports. 3) Multi-language support server-side. 4) Full text searching using Lucene. 5) Modify how branches are handled (I roughly scoped this out in a long ago post to this list). 6) Concurrent versioning. 7) Folder-level security. I think 6 and 7 will slip to a future release. I'd be very interested to hear what's on everyone else's wish list. Also, I'd be curious to hear how others see the future of SourceJammer. It's strength, in many ways, I think, is that it's a "little" source control system. Easy to install and administer. Simple to use. I'm tempted to see it growing down the road into a feature-rich competitor to Subversion. But on the other hand, perhaps that's something SJ should never become because it might lose it's niche. It would be neat to have a very rich branch and merging functionality where you could create a sandbox for each developer and a system of promotion from sandbox to development to production branches. But maybe that's the wrong way to go. I definitely would like so hear some thoughts. Also, Marc, what are the bugs that are causing you problems? --Rob --- Timo Haberkern <[EMAIL PROTECTED]> wrote: > Hi Marc, > > --- Marc Palmer <[EMAIL PROTECTED]> wrote: __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ SourceJammer-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sourcejammer-devel
