@emanuele is still in code edit mode. :D
Thank you all for your effort and spended time to reach the final version! :)
Ehm... Where is it? :o
/me points Jorin at the "[WIP]" (Work In Progress) part of the subject. :P
I'm in the middle of transferring a site, give me half a day. ;)
Oh sorry, didn't know what WIP stood for. O:-) Sure, take your time.
I just found a last minute (well, second) bug worth fixing, I'm re-uploading the packages now.
I see a tagged version :D
Congrats to the Elk team for this milestone. I can't wait to see 1.0 in action soon.
Good job! :)
If I want to upgrade from Beta 2 should I run instal.php?
Nope, just overwrite the files (except Settings.php and Settings_bak.php of course).
Opinion: I was considering releasing release candidates on a weekly basis (so in two days it would be out RC2).
I should also be able to create packages to update from the package manager rather quickly, so it may be an option as well. In case of packages, what would you prefer: a straight replacement of the files, or the classic "find&replace" within the files?
Honestly I would prefer the second, but the first wouldn't be a problem.
Actually, now that I think about it, weekly (or bi-weekly or monthly) releases would fit very well the beta stage, so that anyone would keep their packages up-to-date. I have work a bit on automate the release... But that would be better in the release-cycle topic. :P
Release candidates should be candidates for release, aka a version that you think is ready to be stable. They shouldn't be time-related milestones, or just released when 'it seems reasonable' to have another. Don't fall into the SMF trap of appeasing the masses with releases!
Release early, release often, yes. But don't release if you seriously don't think it's ready. Make sure your release
candidates are worthy of the name.
How many release candidates are you planning to release? I thought after RC1 you will give us the final in a few weeks of bugfixing? O:-)
I don't know if you know that I have half a dozen users who are testing a migration of our forum right now, which runs now with RC1, and we document all found bugs and errors at the moment. We thought it would be clever to collect them for a while and give
@TE this list in a few days or weeks, when no new errors are found.
If you release another RC every week, I feel the urge to stop our test right now! I don't want to install another RC every week and will not force my members to test all of the errors they found again, if the error is fixed or not... And test it with another RC. And again with another RC. And again. And again... Oh, and maybe there are new bugs... ::)
Not happy with this, no. :(
Well, it is a question. :P
BTW,
@Jorin I would suggest you to report the bugs as you find them, I think it's easier to see them one by one and fix them as they come. ;)
Sure. You will get the information you need to fix the errors as detailed and exact as possible. Give us just a few days please.
Time is not problem for me. ;D
If you wantyou can also submit the patch if you already know the fix! :D
Oh no. I'm not into code. :-X
Oooppsss, just came across this beautiful post. Congrats to everyone.
I've few things in my mind, and it has some great ideas to break things ;D. Congrats once again everyone :)
Don't worry, we have a branch all set for the breaking, in fact it may already be broken :D
https://github.com/elkarte/Elkarte/tree/development
thats the 1.1 branch, already underway :D
So, so, so, no new bugs? O:-)
/me feels it may be time then for an RC2...
Well for sure we will need one O:-) Nothing "major" in RC1 but enough small tweaks that we should make an RC2 available. Do we want to wait a full month between released to try and capture some more bugs?
I guess we can start prepare stuff and then have it ready for the "1 month after RC1 release".
It's 2 weeks from now, so it's a good moment to start.
Though I would not release the final the 17th of August. Either the 1st of August or the 1st of September. (I'd say 1st of August just because I darn want to start working "hard" on the dev branch again ASAP! ... not that I'm not working on it, just it's funnier to have more freedom to make stuff fly around. :P)
Sounds good to me :D ... and I have a bunch of things I want to start doing on 1.1 as well !
Darn, there are already 190 commits since the tag RC1!! LOL
I'll bump the version today, I'd ship the RC2 on Monday and plan the final for the 1st of August, three weeks should be more than enough.
Lots and lots of tweaks .... good thing is that I can only recall a very small number of bugs, but there were some !