Steemit Development Timeline - Why "Coming Soon" might not seem very soon
Many of you are familiar with my Steemit.com Development Updates series, which provides the community with information about what is going on in the Steemit.com GitHub development project. It is a good way for the community to get a glimpse into what the Steemit dev team is working on.
My report often says changes will likely be released "soon". I have seen a lot of comments from people wondering what "soon" is, and when to expect features to show up on the live site. I come from a development background - so what seems "soon" to me (one to two months) is probably not the same as "soon" to many of you :)
Hopefully this process will give you a better view into what all takes place, so you can better understand why some of the changes might be taking a while to show up on the live site.
Note - Not all changes follow this exact process, and there is actually more to it than this. This is just a general overview of the process, to give you an idea of what is taking place.
- Usually before work is started, an issue is opened. This is to track the change, as well as allow the community and development team to discuss it. A lot of the time, issues will stay open for a long time before they are worked on. This can be so that the community can discuss them, or because the developers are focused on higher priority changes.
- Once an issue is open, some developers may start to look into the code, and 'unofficially' try out some changes to see what the issue involves. This might be happening in the background, so sometimes it can be hard to tell initially if an issue is actually being looked at.
- If a developer decides to officially work on the change, they will usually assign the issue to themselves. This lets the other developers and community know that they are going to be working on the issue.
- When changes are made, they are introduced into the GitHub system as "commits". A commit is an actual change that to the code, which other developers can review - but it is not officially checked in to the 'main code base' yet. At lot of changes will get to this point, but never make it into the final release because there are either issues with the code change, or the dev team / community doesn't like the changes that are being made.
- Once the developer feels that the change is ready, they will submit what is called a "Pull Request". This is the official way to submit a set of changes to the actual Steemit code base. Submitting a pull request still does not actually check the changes in yet, and it is not a guarantee that the changes will be accepted. It is just the first step in the process to get them there.
- Once the pull request is submitted, it goes under a period of intense scrutiny/review. People will look for things that could be wrong, and test it to try and find issues. At this point the change may be sent back for more work to be done, or completely rejected.
- If the pull request passes all of the tests/reviews, then it will be accepted and merged into the branch. At this point, the change is actually getting close to being released onto the live site.
- Once the change is checked into the branch, it will still undergo a lot more testing and review before it is put onto the live site. It is still possible at this point for issues to be found, at which point the change would need to be rolled back.
- After the change has been thoroughly tested and reviewed in the branch, it will become part of the official release to be launched on the site. I do not have much info on this process, but basically the Steemit team will decide when and how to launch the release.
- The release is finally applied, and the change is up on the live site!
Hopefully now you will all have a better picture of where things are at when I talk about them in my "Development Updates" series. If you have any questions, let me know and I will do my best to answer them.
If any of the developers who have gone through this process have changes to suggest, please make suggestions for revisions in the comments, or message me in Steemit chat :)
Also -
If you want to view my application for witness, you can check it out here.
If you think I'd make a great witness, you can vote for me here :)
I really appreciate what you're doing here. From my experience in gaming, devs explaining what they're up to was a sign of a healthy community, I don't think it's any different here.
What you've been doing is a real service to the community, and very hard to do. Not only are you translating dev-speak into human-speak, but you're doing it only with insight into GitHub activity.
I'm super impressed and wanted you to know that your hard work is noticed and appreciated. :)
Awesome, thank you very much for your kind words :) I'm glad that it is helping!
Thank you for explaining. I recently had my brother-in-law's brother-in-law explain how github works with the pull requests. I think steemit does a great job of addressing issues. Some need more attention, but we are a young company with unlimited growth potential and some incredibly talented developers working behind the scenes.
Cool
Quite Understandable
Thx For What You Do.
A REALLY AWESOME POST!
Thanks for sharing this!
I can see why it takes a "long time" to make changes. My favorite part is the intense scrutiny that potential changes undergo BEFORE they are changes!
I LOVE This and feel that it is such an awesome community standard. Everyhing should be this way!
With that being said I do feel changes are happing "too slowly" as there have been very clear issues and objectives for quite some time. Also the people in charge have a a fair amount of capital to fund simple code changes for already distinguished issues.
Thanks again for sharing and all your contributions to this community!
Thanks for your feedback/thoughts, and I'm glad you liked the post. Out of curiosity, which are the features that you are most concerned about? I might be able to give some explanation as to why certain features aren't getting priority at the moment.
Fantastic overview of the process for a greater insight for all!
Thank you for taking time and explaining the process.
Is there an open issue for giving our feed back to us? If not then it should be :)
I'm not sure what you mean. Can you please elaborate?
I am sorry that I didn't explain it well. On a Steemit UI under home link the list of users posts and all reblogged posts is displayed after the last UI update. How can we see our posts only? A checkbox, sublink, another tab, whatever, ...
This is what I meant with 'giving our feed back' :)
Thank you very much.
Ah, ok. I know they are planning to make a change soon to distinguish between regular and resteemed posts in your feed. @bitcoiner submitted a pull request for it, which was approved last night. I don't know if they are going to do more than that though. The feature you are requesting is part of the "wish list", so I know it is at least on their radar.
When I started in IT programmers were the bane of my existence. Fire drills to shut down receiving, production, and shipping were a regular occurrence when software updates were released so the programmers could restore a backup. Of course explaining to each department why they had to redo an hour of work was always fun!
While I love to see improvements, I'd rather wait until it has been tested.
Great post on the inner workings.
Hi @timcliff, I just stopped back to let you know your post was one of my favourite reads today and I included it in my Steemit Ramble. You can read what I wrote about your post here.
Thanks @shadowspub! As always, you do a great job curating :)
thank you @timcliff you are very kind
I liked your article. Helps you like mine ♥ @siams
Thanks :)
This post has been linked to from another place on Steem.
Learn more about linkback bot v0.4. Upvote if you want the bot to continue posting linkbacks for your posts. Flag if otherwise.
Built by @ontofractal