posted by
NCommander
on Tuesday April 01 2014, @03:31AM
from the the-muffin-welcomes-you-to-the-future dept.
from the the-muffin-welcomes-you-to-the-future dept.
I'm pleased to announce that our site upgrade appears to have been successful, and as promised, here's the list of major changes rolled out in this upgrade. Our muffin overlord however has instructed to leave some items off this list so they can be announced separately as some sorta big surprise. The staff managed to nod their heads and agree as they fail their save rolls against mind control.
Muffincode 14.04 Changelog
Muffincode 14.04 Changelog
- CSS and UI revamps, including a much cleaner user control panel
- Submissions now get properly formatted from the get go
- Lameass filter now reports why you're lame
- REDACTED
- REDACTED
- REDACTED
- REDACTED
You can download the latest hot piping tarballs here
The muffin has granted me a sliver of free will to talk about our update and upgrade policies.
Right, I realize that this is a pretty small update, even taking in account the features the muffin has prevented me from announcing, but I wanted to go into how we're going to do site updates, and what does this mean for you.
I feel that its important that we upgrade the site in a consistent matter so people know when updates are coming. Right now, we're still working on finalizing the specific QA and release processes, but the current plan is to release new versions of the code every two months, with YY.MM version scheme. Our plan is that the site database will remain backwards compatible across one major release, so if we roll something out in 14.06, and you guys hate it, we can revert to the previous version without blowing the site up in the process. This also means if we blow the site up, reversion is trivial.
However, two months is a relatively long time to go between updates, especially ones implementing major functionality (something I'll talk about later), so we'll also be doing point releases which are backports from the master branch to the current stable branch. We'll do these as needed and post about them here when we do it.
We are working to try and squish some of the more major remaining bugs in the site, and we welcome anyone to come join us on IRC and join the dev team. As far as major user facing bugs, we're aware of the timezone one (which has remained illusive to fix), and UTF-8 is still wonky (we found the cause, still working on the fix). I hope to get both of these fixed in point releases in the near future.
I'll have a more in-depth write up on how we'll be managing site development hopefully this week, but until then, leave your feedback below, and know that the muffin is always reading.
NCommander adds: Fixed a typo with the versioning scheme
I feel that its important that we upgrade the site in a consistent matter so people know when updates are coming. Right now, we're still working on finalizing the specific QA and release processes, but the current plan is to release new versions of the code every two months, with YY.MM version scheme. Our plan is that the site database will remain backwards compatible across one major release, so if we roll something out in 14.06, and you guys hate it, we can revert to the previous version without blowing the site up in the process. This also means if we blow the site up, reversion is trivial.
However, two months is a relatively long time to go between updates, especially ones implementing major functionality (something I'll talk about later), so we'll also be doing point releases which are backports from the master branch to the current stable branch. We'll do these as needed and post about them here when we do it.
We are working to try and squish some of the more major remaining bugs in the site, and we welcome anyone to come join us on IRC and join the dev team. As far as major user facing bugs, we're aware of the timezone one (which has remained illusive to fix), and UTF-8 is still wonky (we found the cause, still working on the fix). I hope to get both of these fixed in point releases in the near future.
I'll have a more in-depth write up on how we'll be managing site development hopefully this week, but until then, leave your feedback below, and know that the muffin is always reading.
NCommander adds: Fixed a typo with the versioning scheme
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
(Score: 3, Funny) by naubol on Tuesday April 01 2014, @03:53AM
Hwat happened to it? Did google hack SN and delete it?
(Score: 2) by NCommander on Tuesday April 01 2014, @03:56AM
I pushed it back an hour to prevent two stories from going out at the same time. I already posted this the moment that one came out of the queue. It will reappear in approximately 45 minutes from now.
Still always moving
(Score: 3, Funny) by Hartree on Tuesday April 01 2014, @04:07AM
Ah crap. ncommander's playing with his muffins again. And in public, no less.
(Score: 3, Funny) by davester666 on Tuesday April 01 2014, @04:28AM
How about, say a week or two before you roll out each revision, you make a beta site which runs the updated code.
Then, you randomly punt people who normally would get the current version over to the beta site.
What could go wrong?
(Score: 4, Interesting) by NCommander on Tuesday April 01 2014, @04:34AM
We're actually planning to do this (a feature tentatively called "edge") where users can opt-in to try the latest and greatest on the main site. Unlike some other sites, we'll be responsive to feedback and criticisms :-)
Still always moving
(Score: 2) by Techwolf on Tuesday April 01 2014, @04:36AM
If a comment deserves a -1 funny, that one is it. :-)
(Score: 2) by rts008 on Tuesday April 01 2014, @08:08AM
I have mod points, but could not apply them to your comment, due to there not being a '-1, not funny' mod category.
(Score: 1) by G-forze on Tuesday April 01 2014, @05:15AM
Seems to me the versioning is YY.MM. Maybe fix summary?
That aside, great job! Thank you for all your hard work.
If I run into the term "SJW", I stop reading.
(Score: 2) by NCommander on Tuesday April 01 2014, @05:25AM
Good catch. Fixed.
Still always moving
(Score: 2) by Koen on Tuesday April 01 2014, @12:37PM
Does this imply you will close down SoylentMuffins in 2114? Think of the mufflets!
/. refugees on Usenet: comp.misc [comp.misc]
(Score: 2) by captain normal on Tuesday April 01 2014, @06:55AM
Isn't everything tied to UTC? What's wrong with that? NTP is tied to UTC. As a sailor I'm used to dealing with UTC, it's how we navigate.
The Musk/Trump interview appears to have been hacked, but not a DDOS hack...more like A Distributed Denial of Reality.
(Score: 2) by NCommander on Tuesday April 01 2014, @07:28AM
Under specific cirmstances, Slash seems to not pay attention to UTC, and will show/hide stories based on a users local time.
Still always moving
(Score: 2) by lhsi on Tuesday April 01 2014, @08:30AM
Does the message change after a certain number of submissions is reached? I submitted two to get it over 10 to see if it would but it didn't (I'm wondering if it will omit the "only" part after a certain threshold).
Aside: due to the wording of it, I for some reason have the "10 green bottles sitting on a wall" song stuck in my head...
(Score: 2) by NCommander on Tuesday April 01 2014, @09:14AM
There's a lag between when the stories go in the queue, and when the counter updates. I'll ask paul to write up the specifics as he implemented the nagger. The counter itself vanishes if there are >20 stories in the hopper (which is usually enough to get us through a day).
Still always moving
(Score: 1) by CoolHand on Tuesday April 01 2014, @11:56AM
Mmmmmm....... Muffins...
Anyone who is capable of getting themselves made President should on no account be allowed to do the job-Douglas Adams
(Score: 2) by nightsky30 on Tuesday April 01 2014, @12:51PM
Does it still have to be called slashcode? Can we call it Soylentcode or Soylentcode: The Forked Beta?
(Score: 3) by hankwang on Tuesday April 01 2014, @02:32PM
Put borders around it, change the background color, put a vertical bar on the left, or whatever to make it stand out from the surrounding text other than an indent.
Avantslash: SoylentNews for mobile [avantslash.org]