Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I have a custom SharePoint solution which requires several list instances on a particular site (SPWeb). Now some of these lists are generic, for example a 'Pages' document library, wheras others are highly specific custom lists.
My question is which (if any) apsects of customisations should be cleaned up on feature deactivation. My instincts would say that generic lists which may be used by multiple solutions should be left, but the more specific customisations should be cleaned up. Does anyone have any experience of and/or advice on this type of sceanrio?
Its really hard to come up with a strict rule, as it will depend on your specific solution, however I would start with something like this:
On deactivation a feature should remove any artifacts created during feature activation that:
Have not been created by an end user AND that end users could not reasonably expect would remain
Is not required by any other feature, or that causes a failure in the broader solution it supports
Does not prohibit the re-activation of the feature at some later time.
On the project I'm currently working on we created a new exception for preventing the deactivation of features. We found that in many cases the activation of features was a one way street. This was largely because a solution was typically made up of a number of features, and disabling one caused a break down in the entire solution.
Often, a site only existed in order to host the feature, disabling the feature then left no purpose for the site.
Adding on to Daniel...
If another feature depends on this feature, they should be activated & deactivated together through feature dependencies
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
What are some ways including machine learning that I can use in my projects to generate things related to another. Like related apps, related websites, related products, etc.
I've been brainstorming these are strategies...
one way i can think of is show items from same category. But that would be too broad.
2nd way improves upon previous step, it's to keep track of what people click next and promote that item. Meanwhile keep bottom list randomized to let other relevant items show up and get clicked.
3rd way is to use machine learning and provide training data somehow and use that.
I want something simple but smart, as it gets better with time.
Collaborative filtering is designed for solving exactly this problem. The problem with this approach is that produces good results having a lot of data only. I mean... A LOT. And it's not a really simple thing to use. However, any machine learning technique is not simple. There are some node.js packages for CF available, but I have no idea how good are they.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Can you give several indications (pro and cons) concerning the fact to put the menus of a web application inside the database?
Mainly it depends upon your requirement of your application. Its not always a good approach to bring a drill machine to make hole in sand. Every approach has some limitations and need more efforts if you do apply some alternate approaches.
In cons you can consider
Performance ( to prepare dynamic menu every time you load the master page also the static text less time to process in compare to dynamic)
Configuration will be always an issue while adding or modifying the menu
(Always need a database guy at the time of any change)
Pros
Highly configurable and completely dynamic
Can add/remove the attribute and change the text without affecting anything in code.
We have some solutions also to overcome from the cons
In case of performance we can use caching but everytime the menu change you need to recycle the application pool.
For configuration you can provide a page to control the menu content. (No Sql guy needed)
So as I said earlier you can go either way as your application adopt easily and in much better way.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I'm thinking about joining a free software project in order to increase my knowledge of how this kind of projects works, colaborating with people that I dont know (so far), and my C/C++ skills.
I`ve searched on sourceforge and so on, looking for projects that need developers... so my question is: how to join a existing project? (and find one I like)
Pick one you like/are interested in, look over its bug tracker, and contribute patches. As you demonstrate your ability to work along with the developers, you will generally be offered greater involvement (e.g. direct commit access).
#geekosaur has some good points. (+1)
If those don't work, I would consider looking for the lead developer of a project (preferably one with decent activity and leadership) and asking what areas they would like assistance in.
I promise you, almost every open source project manager would absolutely welcome a fresh face to the team!
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
My current work involves working on a large number of bugs.
We normally (non TFS) would add these to an iteration backlog (grouped into Stories) after estimating and prioritising; then work through, mark actual effort.
I want to try and understand how I would work on these bugs using the TFS Agile template as intended. But am really struggling to find best practices and examples specifically for bugs for the TFS Agile template in TFS2010.
Cheers, Nick
I hear some parts in your question:
"Add these to an iteration backlog": you can use the iteration path of the work items. Best practice is to create an iteration called backlog.
"Grouped into Stories": In TFS 2010, the default traceablity is that on a User Story you define the Test Cases which validate the User Story. The Bugs are reported against the Test Cases.
"Estimating": You can use the Remaining work field for that
"Prioritsing": You can use the Stack Rank field
"Mark actual effort": Use the Completed work field
What we have been doing is:
Raising bug during testing by a tester.
During iteration planning we may decide to allocate X amount of time to fix outstanding bugs, so we creat a bug fixing story for that iteration of X story points.
Bugs are chosen that we think should be fixed within the iteration, a task is created for each bug along with a time estimate and any high level technical details. Note the task is created as a child of the story and also related to the bug.
The key is that bug work items are not developed against directly, a related task is.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
I began using a bugtracker (www.bugnotes.com) so I am new to this... And I am easily adding bugs, makes sense. However some of these bugs would be fixed if I were to implement a given feature or perform some refactoring. So how can I track todo-list type things effectively, and don't these kinds of tasks tie into bug tracking? I guess what I am asking for is tool that tracks both bugs and features since they are all code changes.
Oh and putting minor fixes as #TODO or //TODO: is great actually, I like this for minor things, just not big things like refactoring, or changing a driver or a library.
Also, I was using a text file but the problem with that is that so much of what is typed into there becomes old and therefore the whole thing is kind of useless to me.
Any bug tracking system can be used to log bugs, features or general to-dos, as each is comprised as some form of work unit. The advantage of storing these in a bug tracking system is that all outstanding tasks are visible and can be prioritised. If you rely on TODO in the code then it is difficult to see these at a glance and hard to prioritise or see where you are with them. As a result, in my experience if you rely on TODOs then the list of these only ever gets longer. If you have some code that is incomplete, I think it's better to turn the TODO into a bug entry and then replace the TODO with the bug id, so you have a link between the code and the bug. A side benefit is that when you actually do the work and commit to version control, you can also add the bug id in the checkin notes and so you've got a permanent record of when the change was made.
If you have lots of TODOs already then it may be worth looking at a Hudson continuous build system, and add the Static Analysis plugin, so that you'll get a daily graph of the number of remaining TODOs, cross referenced with the source. That will at least present everything in one place and give you a burn down graph as you fix each TODO.