You know, there was a thread the other day about a new release announcement for some IDE. It was quickly removed, on grounds that the Hacker News FAQ says you shouldn't repost something "If a story has had significant attention in the last year or so".
I remember thinking that it was a real stretch to interpret different release announcements, separated by months, as "duplicate" posts. But this was coming from dang himself, so I guess that's the authoritative view.
Just pointing out that Gitlab operates on a more or less monthly release cadence. Pretty much every release gets an announcement thread on HN's front-page for the full day. And usually there's a separate front-page thread or two in between, to announce stuff in upcoming releases. I've never once seen any of this removed, or even questioned.
It's funny, I read your post and thought you must be talking about Lazarus. I did some searching and (I think) found the thread in question (I actually didn't see the submission, but was thinking of the 17 day old one that was marked a dupe and later unduped - which killed the momentum it had):
I too would like to see some clarity on this rule. I was bummed the 17 day old one was marked a dupe. I personally love Lazarus discussions, it's so interesting to look back on Delphi and think about how little our tools have improved. I think they are so popular because a lot of developers share that sentiment.
(Note: obviously my opinion, not the actual rules)
I do think the rule should be based on the content of the release rather than the timing. If the software contains major new features every month that could be relevant to the HN audience I see no reason to remove the post, it's _new_ information being posted on Hacker _News_. (I haven't seen the referenced IDE update post so I don't have an opinion on it either way.)
I’ve submitted it a few times, just because I use it and like it, interested in discussion about it. I don’t know if I agree with the rule (a whole year?), but I’ll stop submitting it.
Overview of the three main improvements in this release:
1. JavaScript coverage in SAST
GitLab Static Application Security Testing (SAST) scans source code and helps to detect potential security vulnerabilities early in the pipeline. In 11.8, we've added SAST support for JavaScript, building on top of our existing node.js support. Now any JavaScript file can be scanned, like static scripts and HTML. A vital practice in DevSecOps is to scan code changes with each commit, and with this change, we're covering one of the most popular web languages, helping you to find JavaScript risks as early as possible.
2. GitLab Pages for subgroups and templates
GitLab Pages got a whole lot better this release, with two key improvements. First, we have introduced GitLab Pages support for projects in subgroups, enabling these projects to easily publish content to the web. GitLab 11.8 also bundles our most popular templates for Pages, so users can get started with just a single click.
3. Error Tracking with Sentry
Application errors provide important insight into the health of your application, and can help detect problems without waiting for users to report them. GitLab 11.8 can now display the most recent errors directly within the project, making them easier and quicker to find and take action on.
Gitlab is great and I have used it for years but I recently switched to Gogs for self hosted repositories because it is much faster, easier to set up and walk in a park to maintain. It doesn't have all the features (bloat) that Gitlab has but it can probably satisfy >95% of git users.
Hello! Since GitLab is a single application that covers the entire software development lifecycle, we're a bit "bigger" than Gogs, which only tackles SCM. We have a plan to make GitLab use less resources, including forming a team to specialize in this area, and we're really grateful for your feedback. :)
I really like the update pace of Gitlab. Our teams are all based on an on-prem EE (low tier) and it's been a pleasure to receive a steady stream of valuable updates.
Passing on all the good things that Gitlab does for us already; I _really_ wish gitlab would push to make more of the Project Management features accessible to the lower tiers (maybe even CE). Epics and Roadmaps linked to Gitlab's SCM and DevOps features would be a _real_ contender to JIRA/Confluence in the market but it's currently hidden behind a very steep ~100$/m "ultimate" plan.
GitLab Community Advocate here. Thank you very much for the feedback. I understand your desire to move some features to the lower tiers and that's a good sign for us that we are on the right path with our offerings.
From time to time it happens that we move some features to the lower tiers or even core/free tier.
Thanks for your comment. Glad to hear you like the update pace. Regarding epics we're considering moving them to a more affordable plan while keeping the roadmap in Ultimate. But we're not close to a decision.
Funny thing, when I joined the team at GitLab over a year ago I was really annoyed by this since I'd been using PR for the better part of a decade. Now I'm so used to saying MR that PR sounds very strange. All in all, "merge request" is a more accurate term and no one ever gets confused about it like https://stackoverflow.com/questions/21657430/why-is-a-git-pu... I think it would be great if other tools just called it an MR as that seems to be the term that is easier to understand.
Since GitLab for Education was announced I've been trying to get our college signed up for it, but it's been difficult so I was hoping I might be able to share some GitLab for Education Requests:
Working in a community college it's been really tricky to get the agreement signed for us to take advantage of this at all (that's more of an issue with the way we work in particular, but I just wanted to throw it out there that it would be nice if we could sign up for the licenses completely online without needing to wait and get an agreement signed because for example our president doesn't want to do an esignature so that means sending it over to their office for signature, waiting a long while, getting it back, and then finding out our deadline passed and haven't to try it all over again so if that process could be changed, or better yet removed, that would be great).
Related to the GitLab for Education license limitations...I originally though the Education licensing would cover usage for our IT Department staff as well, but it definitely seems to be limited to just Faculty/Staff type usage which ends up being a bummer for us since now I can't promote it anymore internally with us a free option we can sign up for anymore and other ideas I was potentially thinking of (the Group Issue Boards seemed like it could potentially be a nice way to organize Kanban Boards across the college and make it so that staff from other areas outside of IT could make use of Kanban Boards too...we've been using Kanboard inside of IT for a few years now, but haven't made a strong push to have other departments use it). In terms of affordability, that would limit us to licensing GitLab primarily for IT stuff only + for 10 users that's already going to be a pretty big cost for our small college / IT department.
Lastly, I know there's Wiki functionality and GitLab Pages already and that can be used for documentation to a degree, but is there any work towards building/including some sort of Confluence alternative into GitLab as well?
Right now we'd like start using some sort of nice, comprehensive documentation option, but I'm not really sold on Confluence at the moment. Admittedly, right now with the info about us needing to license GitLab for our IT department staff as well being fairly new to me that's thrown the whole idea of using GitLab out the window (almost), but the lack of a Confluence option built-in to GitLab would be another potential blocker for us (I do like the idea of having everything all under one system if possible to simplify usage for us).
tldr: If you can make edu licensing completely free (for staff too) and simple to use/signup for (without an agreement needing to be signed), plus add a Confluence alternative that would be awesome!
Thank you for the detailed feedback! We love to hear that we're doing something well, but also like to discuss if there is something that can be improved.
> It would be nice if we could sign up for the licenses completely online without needing to wait and get an agreement signed
That sounds reasonable, and it doesn't seem to be an issue only with your institution. We already have an issue for automating the application process for the educational license. [1] The proposed solution would resolve all concerns described here.
> I originally though the Education licensing would cover usage for our IT Department staff as well
The primary goal of this program is to help students catch up with the latest technology in software development as early as possible, and we think that we managed to do this with the current setup. However, we would love to discuss other options regarding this program's limitations. Please open an issue [2] - we would love to hear your suggestions.
> Is there any work towards building/including some sort of Confluence alternative
Can you please tell us more about what part of Confluence do you think is missing in GitLab? You can use this page as a reference - there are all stages of development that are covered by GitLab. [3]
Thank you again on your feedback, it is greatly appreciated.
[+] [-] StevePerkins|7 years ago|reply
I remember thinking that it was a real stretch to interpret different release announcements, separated by months, as "duplicate" posts. But this was coming from dang himself, so I guess that's the authoritative view.
Just pointing out that Gitlab operates on a more or less monthly release cadence. Pretty much every release gets an announcement thread on HN's front-page for the full day. And usually there's a separate front-page thread or two in between, to announce stuff in upcoming releases. I've never once seen any of this removed, or even questioned.
[+] [-] rudedogg|7 years ago|reply
https://news.ycombinator.com/item?id=19169397
I too would like to see some clarity on this rule. I was bummed the 17 day old one was marked a dupe. I personally love Lazarus discussions, it's so interesting to look back on Delphi and think about how little our tools have improved. I think they are so popular because a lot of developers share that sentiment.
[+] [-] yutghgh|7 years ago|reply
I do think the rule should be based on the content of the release rather than the timing. If the software contains major new features every month that could be relevant to the HN audience I see no reason to remove the post, it's _new_ information being posted on Hacker _News_. (I haven't seen the referenced IDE update post so I don't have an opinion on it either way.)
[+] [-] markdog12|7 years ago|reply
[+] [-] michaelbuckbee|7 years ago|reply
[+] [-] jjeaff|7 years ago|reply
[+] [-] sytse|7 years ago|reply
1. JavaScript coverage in SAST
GitLab Static Application Security Testing (SAST) scans source code and helps to detect potential security vulnerabilities early in the pipeline. In 11.8, we've added SAST support for JavaScript, building on top of our existing node.js support. Now any JavaScript file can be scanned, like static scripts and HTML. A vital practice in DevSecOps is to scan code changes with each commit, and with this change, we're covering one of the most popular web languages, helping you to find JavaScript risks as early as possible.
2. GitLab Pages for subgroups and templates
GitLab Pages got a whole lot better this release, with two key improvements. First, we have introduced GitLab Pages support for projects in subgroups, enabling these projects to easily publish content to the web. GitLab 11.8 also bundles our most popular templates for Pages, so users can get started with just a single click.
3. Error Tracking with Sentry
Application errors provide important insight into the health of your application, and can help detect problems without waiting for users to report them. GitLab 11.8 can now display the most recent errors directly within the project, making them easier and quicker to find and take action on.
[+] [-] Jnr|7 years ago|reply
[+] [-] Suri_GitLab|7 years ago|reply
[+] [-] W-Stool|7 years ago|reply
[+] [-] StyloBill|7 years ago|reply
[+] [-] bbeausej|7 years ago|reply
Passing on all the good things that Gitlab does for us already; I _really_ wish gitlab would push to make more of the Project Management features accessible to the lower tiers (maybe even CE). Epics and Roadmaps linked to Gitlab's SCM and DevOps features would be a _real_ contender to JIRA/Confluence in the market but it's currently hidden behind a very steep ~100$/m "ultimate" plan.
[+] [-] dsumenkovic|7 years ago|reply
I wanted to share few more words on how we are trying to be the good stewards, you can find more about our stewardship rules and promises here https://about.gitlab.com/company/stewardship/#what-features-...
[+] [-] sytse|7 years ago|reply
[+] [-] laktak|7 years ago|reply
[+] [-] williamchia|7 years ago|reply
[+] [-] orware|7 years ago|reply
Since GitLab for Education was announced I've been trying to get our college signed up for it, but it's been difficult so I was hoping I might be able to share some GitLab for Education Requests:
Working in a community college it's been really tricky to get the agreement signed for us to take advantage of this at all (that's more of an issue with the way we work in particular, but I just wanted to throw it out there that it would be nice if we could sign up for the licenses completely online without needing to wait and get an agreement signed because for example our president doesn't want to do an esignature so that means sending it over to their office for signature, waiting a long while, getting it back, and then finding out our deadline passed and haven't to try it all over again so if that process could be changed, or better yet removed, that would be great).
Related to the GitLab for Education license limitations...I originally though the Education licensing would cover usage for our IT Department staff as well, but it definitely seems to be limited to just Faculty/Staff type usage which ends up being a bummer for us since now I can't promote it anymore internally with us a free option we can sign up for anymore and other ideas I was potentially thinking of (the Group Issue Boards seemed like it could potentially be a nice way to organize Kanban Boards across the college and make it so that staff from other areas outside of IT could make use of Kanban Boards too...we've been using Kanboard inside of IT for a few years now, but haven't made a strong push to have other departments use it). In terms of affordability, that would limit us to licensing GitLab primarily for IT stuff only + for 10 users that's already going to be a pretty big cost for our small college / IT department.
Lastly, I know there's Wiki functionality and GitLab Pages already and that can be used for documentation to a degree, but is there any work towards building/including some sort of Confluence alternative into GitLab as well?
Right now we'd like start using some sort of nice, comprehensive documentation option, but I'm not really sold on Confluence at the moment. Admittedly, right now with the info about us needing to license GitLab for our IT department staff as well being fairly new to me that's thrown the whole idea of using GitLab out the window (almost), but the lack of a Confluence option built-in to GitLab would be another potential blocker for us (I do like the idea of having everything all under one system if possible to simplify usage for us).
tldr: If you can make edu licensing completely free (for staff too) and simple to use/signup for (without an agreement needing to be signed), plus add a Confluence alternative that would be awesome!
[+] [-] btasovac|7 years ago|reply
> It would be nice if we could sign up for the licenses completely online without needing to wait and get an agreement signed
That sounds reasonable, and it doesn't seem to be an issue only with your institution. We already have an issue for automating the application process for the educational license. [1] The proposed solution would resolve all concerns described here.
> I originally though the Education licensing would cover usage for our IT Department staff as well
The primary goal of this program is to help students catch up with the latest technology in software development as early as possible, and we think that we managed to do this with the current setup. However, we would love to discuss other options regarding this program's limitations. Please open an issue [2] - we would love to hear your suggestions.
> Is there any work towards building/including some sort of Confluence alternative
Can you please tell us more about what part of Confluence do you think is missing in GitLab? You can use this page as a reference - there are all stages of development that are covered by GitLab. [3]
Thank you again on your feedback, it is greatly appreciated.
[1] - https://gitlab.com/gitlab-com/marketing/community-relations/...
[2] - https://gitlab.com/gitlab-com/marketing/community-relations/...
[3] - https://about.gitlab.com/product/
[+] [-] hitekker|7 years ago|reply