Deployment of BuiltInFieldDefinitions #1088
Comments
|
No, that's fine, we totally understand. It seems to be a growing trend over the last month, more people asking this feature. Mostly, Europe-based companies and people which have to deal with multi-languages. Current challanges is to make sure it works well and covered with testing. That comes to a highly disposable and repeatable installation of SharePoint farm for regression testing - with various language packs so that we can run and cover regression testing. The way it might work is that we would provide a global swith and underlying C# service, a provider which would handle default fields for varuous languages. That way, we still would be able to go with default English and full backward compatibility or switch to other supported language across the board. SPMeta2 itself would benefit from such service as well. ETA might be around 1-2 months. We are about to release Pretty much, as already mentuoned, a few month of delaying on releases were all about getting underlying regression testing infrastrucutre right - ability to spin up farms in 20-30 minutes from scratch under CI. |
|
Hey guys, i'm back ;) Thanks Anton for this detailed explanation of what has been going on behind the curtain in the last couple of month. It's really impressive stuff you're working on and I can't wait to start exploring metabox. There are so many more great ideas in the pipeline and I'm really looking forward to them. However, please let me give you a honest feedback while keeping in mind that I really appreciate what you've done by releasing SPMeta open source. First of all you're a company which has to earn money and not here to make our life better. But since we're using SPMeta in every project, we also depend on your support when it comes to new releases. 3 month ago I created 3 pull requests (easy changes) which we're using in 2 of our projects right now. Since there hasn't been a official release since July 11th (5 month soon) we're running custom builds of SPMeta which is not what I would like to do and can't tell my customer because they would be furious about it compliance whise. Please don't get me know, I don't want to come across ungrateful and bitching, but I feel that since the acquisition things have changed not only regarding releases, but also communication wise. I feel bad for every time I have to ask for a release or something like that, because this is open source and I don't want to sound demanding or rude. When I ask I get almost every time a reply within hours or days, but only if I start a discussion and in the end suggested time schedules did not know through in the last 8 month. @avishnyakov the information you gave me here could have been on subpoints blog, twitter or yammer to let people who use your software know what's going on. If your focus is moving on other projects and this is most likely the situation for the future of SPMeta, please let me know so we can make our decisions based on that. |
|
@andreasblueher fair feedback, taken with all seriousness. @avishnyakov and we are fully aware of the situation. PRs Communications Unclear future of SPMeta2 Good point raised - we should have a roadmap page or something, stick to releases and make sure the future is known.
Finally, what would you suggest we can do to fix all this? |
|
@SubPointSupport a roadmap would be great! You do assign GitHub issues to release and milestones but some of them have been moved between milestones several times without any visible progress. A road map including some "behind the scenes" tasks and their progress would increase transparency regarding whats happening and why a release might be late. If there is nothing to release, don't release a new version. If there is something new, even something small like one or two bugfixes, just release it. If someone doesn't want to upgrade he doesn't have to, others might wait for this specific one. Also if you would start shareing your thoughts about the future of SPMeta, if you would start having a roadmap and maybe elaborate on where you think SharePoint development will move in the future and which role SPMeta could have there .. this overall would make me happy and would help to develop our on stragety. |
|
On PRs today and this week. |
|
Hey guys, it's been more than a week and no news yet again. Just to be clear, anything like "We ran into some issues, working on it" or "Something more important came up, will have to move to next week" would also be fine, but verbal commitments without results are not pleasing |
|
@andreasblueher, delaying due to upcoming xmas and metabox related work. We are still working on mentioned early "metabox" project to get dev/regression environments right for SP2013/2016. I might have mentioned early that the very root of the issue and slowdowns is that we can't scale contribution and regression testing not internally neither publicly with other people contributing. All comes down to an ability to get dev/regression environment spin up. Both us and YOU should be able to do this, and that's the trickiest part we have been trying to figiure out over the last month. This is also a tech reason on why other projects were on hold for a long time. Semi-manual setup is a reasoning behind with all consequences: poor doco, web site updates, and pretty much any dev done within ecosystem. Not a surprise if you are in IT and think about all this. Totally understand frustration around comms and feedback. Not much I can do about this yet but only working to get all right and re-engage the whole ecosystem development. If you need PRs done, could I ask you to raise them again, please? Let me work it our for you. And my personal sorry for not following up on you need, you are right here. |
|
@avishnyakov I'm not complaining it hasn't been finished yet and I'm pretty much in the same situation with 2 of my projects. I have a lot of respect for the work you're doing and I've learned tons of stuff reading and studying your code so I know you how important those changes are. One thing you could do about it is to give somewhat regular updates on your progress. I don't expect anything specific, but something regular. Regarding the PRs I couldn't raise them again as all changes appear to be merged to dev already. |
|
@SubPointSupport @avishnyakov Happy new year! Any updates on your progress? |
|
@andreasblueher, hey, happy new year as well! All looks pretty promising. Initial Metabox dev is completed. It is a wrapper, an enhanced API layer on top of Packer/Vagrant tools to simplify Packer image builds and Vagrant VM managements. @shurick81 and I made initial POC, not we are moving all dev/regression environments internally to metabox both goodfooding it, testing and improving as we go. A few days to go. Once finished, this gives us fully disposable, fresh environments to develop and regression test SPMeta2. Plan it to get early regression feedback by Friday and release over the weekend. The rest comes along pretty smooth; as you don't have to worry about environment maintenance, I personally put a huge bet on re-engaging all goodies around SPMeta2 on scheduled, weekly basis. That includes many things we could not have done early, such as well-tested reverse library and delivery with metapack/nuget based feeds - high stake on January to push these out alone with doco/redesigned web site. |
|
Metabox is going to be moved to a new public repo today/tomorrow. Finalizing doco and little fixes. Once out, we are back to SPMeta2. |
|
Alright, @shurick81 and I made initial release of metabox under SubPoint Solutions repositories: We are still in transition of the internal infra, both dev/regression. It is a mixture of moving to the new platform and fixing up minor issues as we go. The current state of metabox provides us with a mature and highly disposable SharePoint 2013 SP1 environments for both dev/regression, and this is the pivotal point for us to move forward and move faster with SPMeta2 and related projects. Infra milestone is closed, now getting back on dev. I'll provide further updates as we go. |
|
@avishnyakov Thank you for the frequent updates, I really apreciate it. Had a look into metabox but was too much stuff I didn't understand right away. Looking forward to more good news :) |
|
@andreasblueher, agree that complexity is a bit over the top. Below are a few things we are moving forward. More metabox guides are to come as blog/doco platform is solved afterwards.
That already provides an epic automation platform for SharePoint related installs for both Windows and MacOS platforms with the following statistic:
Apart normal dev environments, our regression infrastructure for SPMeta2 is 6-8-10 SharePoint 2013 farms with NCrunch Grid Server Node. Now it's completely automated, disposable and authored via YAML documents with ETA of about half-an-hour to an hour to completely re-create everything. This week's focus is to continue re-platforming of SPMeta2
As you can see, we seem to be halfway through our tech dept open sourcing nearly everything as we solve it. Again, understand that releases have not been out for a while. The bet is a bit bigger than one library, we need this change to get ecosystem wheel moving. |
It's been 3 weeks since the last action on GitHub and I really don't want to start all over again what I've been complaining about in the last couple of month. To be fair I seem to be the only one who is frustrated by this situation which makes me wonder how many people are actively using SPMeta or maybe many have moved to PnP. I don't need another explanation why the lack of feedback and news happenend. Simply tell me honest to god if this will change. If so, when will it change? If your focus is with other projects (like I said, that's totally fine with me) just let me know so I can stop expecting. |
|
@andreasblueher to be fair you aren't the only one who complains, and it is so far a good thing. Keeps us in check. Such feedback is constant, along with "thanks, it just works". Okay, you are right. Enoght is enoght, I struggle to hear and feel your frustration.
Not ideal, we all know. Let me know what I can fix. |
|
|
Put together SubPointSocial account on medium.com, sorting our a few more technicalities before putting posts together. A few noted on the mentioned ticket:
If these are the only changes, we might skip full regression, or run it over the weekend with Mon/Tue release.
Fair point. How we approach the doco might be a good post by itself, there were a few iterations with it. Let's give a few posts up on medium, and then focus on addressing this one. |
|
Confirming aim for Monday release.
|
|
I've watched the medium.com but haven't found any news. Am I doing it wrong? Haven't used this site before ;) |
Our default language in most of our projects is german. BuiltInFieldDefinitions are available in English only. Either way I was wondering if it wouldn't be possible to check while deploying those BuiltInFieldDefinitions which language is currently active and retrieve the correct resources for those languages.
If I should elaborate more on what I mean, please let me know.
The text was updated successfully, but these errors were encountered: