Should we branch RC2 and let dev deal with 2.0?
What do you think?
Or do you prefer to keep dev for 1.1 until it's ready?
Re: Should we branch RC2 and let dev deal with 2.0?
Reply #1 –
I don't quite understand.
Re: Should we branch RC2 and let dev deal with 2.0?
Reply #6 –
Another question.
What is the schedule for the completion of the 2.0 final? How long shall it take approximately? A year? Two years?
Re: Should we branch RC2 and let dev deal with 2.0?
Reply #7 –
Well, my personal goal was to release every 1 year and a half.
Now 1.1 took about three years, so I still guess 1 year and a half, but who knows. xD
Re: Should we branch RC2 and let dev deal with 2.0?
Reply #8 –
I say do whatever makes Elk even more successful.
Re: Should we branch RC2 and let dev deal with 2.0?
Reply #9 –
1.1 is currently in RC status. I would find it not logical to do anything but bug fixes to the release.
If there are major ideas for the future, the pragmatic approach would be to reserver them for the forthcoming release. And the best would make that future release backward compatible so that addons, themes and language support can still be used.
Re: Should we branch RC2 and let dev deal with 2.0?
Reply #10 –
Elk is already feature complete as it is, and plugins can take care of the rest, so im guessing 2.0 and clean slate (not caring about backward compatibility) is the way to go...
Re: Should we branch RC2 and let dev deal with 2.0?
Reply #11 –
I agree, 1.1 and also 1.0 (since most people are using this version) only for bug and security fixes. New features to 2.0 version.
There are also the addons to be considered, without them updated to 1.1 we are stucked at 1.0 version