This project is read-only.

V2 Maintenance

Topics: Rawr.Base
Apr 29, 2010 at 9:38 PM
Edited Apr 29, 2010 at 9:41 PM

Has the development team given any thought to branching the current code base and moving toward maintenence mode for v2? Instead of developing v3 as a 'sub project'

This might make development on v3 more focused on providing functionality and model updates instead of managing build directives for silverlight / v3 all over the place. The latest main development would always be the latest v3 and you could go back and fix issues on 2 independent of 3. Why keep the code lying around for 2 when 3 is where you want to be. 


Apr 30, 2010 at 3:22 AM

It's the same code, actually. Just certain assemblies are build or not build in 2 vs 3.

Apr 30, 2010 at 3:56 AM

Also Rawr3 is not a replacement for Rawr2. Rawr3.WPF will be at some point, but the performance and polish is not there yet to be competitive with Rawr2.

Apr 30, 2010 at 9:08 PM


May 2, 2010 at 4:08 PM

Is there a current ETA on the next v2 update?  Would be nice to calculate rare gems again... :)

May 4, 2010 at 1:45 AM

Thanks luckton, you make my point for me. With a proper branch setup high priority updates like gemming and stuff could be released while other longer tasks (Model Revamp, WPF) could be worked on without breaking the stable code. 

May 4, 2010 at 2:05 AM

Actually, he didn't. Those are completely shared, and there's no such thing as breaking the stable code. We're always working on, and releasing, the most recent version. There's no branching going on here.

May 4, 2010 at 4:17 AM

Correct... We don't have a release cycle that supports branching very well.  We as individual model developer may have our own local dev branch for new features, but given the cyclical nature of releases, I really prefer this over the "standard" branching methodology.  It would undermine the more agile nature of this project.  Most of the issues in the tracker are single check-in type bug fixes.  There is a branch for Rawr3 specific features, but the architecture is solid enough to support common models, and 2-3 different methods of delivering that model to the user: Rawr2 style, Rawr3 Web, Rawr3.WPF. 

I'm glad to work on the project and happy to get the issues fixed as we can.

May 4, 2010 at 6:49 AM

From what I can see you are already in maintenance mode. My original post was coming from another direction, More feature oriented then model fixes. I'm used to a more feature driven cycle that releases often (1-2 weeks). 

Blame git for my branch bias. Its odd for me not to see branches, especially in a product at v2 moving to v3.

It seems to be working for the project at the moment. Keep up the good work.

I look forward to committing some patches once I get acquainted with the code.

May 4, 2010 at 7:44 AM

There's just no difference between maintenance mode and new development mode for us. We just release (usually every 2 weeks, this build has just been especially stable and problem-free, so it's lasted a bit longer) whenever we need to.

May 5, 2010 at 3:27 PM

The inside truth is that Astrylian, being a bear, is usually hybernating and never makes any new releases unless one of the model devs dares enter his cave to poke him awake... 

Coming out of this alive usually means you'd better have mass quantities of prime quality honey.

May 5, 2010 at 4:58 PM

And when he says prime quality we mean, the kind that will knock you on your ass after two samplings, cuz if it takes three he'll roll over on you with all his bear weight.

It's the Bear necessities man, the simple bear necessities of life.

May 7, 2010 at 9:06 PM

A query can a lowly non-programmer like myself apply these check-ins and fixes I see posted in the Source Code section instead of having to wait for a release? 

May 7, 2010 at 9:07 PM

Only by installing Visual Studio and building it yourself. If you're a 'lowly non-programmer', you can't really.

May 8, 2010 at 12:04 AM

/cast [target=OReubens] Tricks of the Trade

/poke [target=Astrylian]

Luckton, actually I feel for you, there are a few bugs that I posted about that have been fixed, just waiting for the next release.  But I DO understand that too-frequent releases sucks for users also (especially those that instist on doing full Armory/Wowhead item updates each time they get a new release.

May 8, 2010 at 2:10 PM

/cast Divine Shield
/cast Hearthstone